View 5962-9466309QXC_6631345.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

s m mmit family - 1 1.0 i n t r o d u c t i o n the monolithic s m mmit provides the system designer with an intelligent solution to mil-std-1553 multiplexed serial data bus design problems. the s m mmit is a single-chip device that implements all three of the defined mil-std-1553 functions - remote terminal, bus controller, and monitor. operating either autonomously or with a tightly coupled host, the s m mmit will solve a wide range of mil-std-1553 interface problems. a powerful risc processing unit provides automatic message handling, message status, general status, and interrupt information. the register-based interface architecture provides many programmable functions as well as extensive information pertinent to device maintenance. in either of the three operating modes, the s m mmit can access up to 64k x 16 of external memory (65,536 x 16). the s m mmit (which derives its name from serial, m- coded, monolithic, multi-mode, intelligent, terminal) is a powerful asset to a system designer solving the mil-std-1553 problem. 1.1 remote terminal features the s m mmit remote terminal (srt) conforms to the requirements of mil-std-1553b, notice ii. in addition to meeting the requirements of the standard, the srt has an extensive list of flexible features to meet any mil-std-1553 interface requirement. 1.1.1 indexing the srt can buffer up to 256 receive messages on a subaddress- by-subaddress basis. upon reception of the specified number of messages, the srt can generate an interrupt by signaling either the host or subsystem that data is ready for processing. the indexing feature is commonly used to implement bulk data transfer algorithms. 1.1.2 buffer ping-pong to support the transfer of periodic data, double buffering schemes are often incorporated into remote terminal designs. periodic data transfer incorporates the use of two data buffers per subaddress. the remote terminal processes messages (receive or transmit) via the designated primary buffer. the host or subsystem uses the secondary buffer to collect new data for transmission or processing data received during the defined time interval. upon completion of the defined interval, the remote terminal will switch the primary and secondary data buffers (i.e., ping-pong). the srt supports ping-pong buffering via a user- selected ping-pong architecture consisting of dual subaddress data pointers. 1.1.3 circular buffers s m mmit circular buffer modes simplify the software service of remote terminals implementing bulk or periodic data transfers. the s m mmit architecture allows the user to select one of two circular buffer modes. the user selects the preferred mode, at start-up, by writing to control register bits. 1.1.4 internal illegalization an internal 256-bit (16 x 16) ram allows for the illegalization of all mode codes and subaddresses. the illegalization ram is accessed at the beginning of message processing to determine if the valid command is prohibited. to eliminate host or subsystem overhead, the s mmm it can initialize the 256-bit illegalization ram during the auto-initialization sequence. 1.1.5 broadcast designed to meet the requirements of mil-std-1553b notice ii, the srt can store all data associated with a broadcast command in separate memory from non-broadcast commands. this feature is user-selected via the descriptor control word and internal control register. 1.1.6 interrupt history a programmable interrupt structure allows the host or subsystem the flexibility to enter 16 interrupts into a 32-word buffer before service. this feature allows the logging of multiple interrupts if immediate service is restricted. the interrupt structure enters an interrupt information word (iiw) and an interrupt address word (iaw) indicating what subaddress or command block generated the interrupt. all modes of operation support interrupt logging. 1.1.7 message information the srt generates a message information word and time-tag (16-bit) for all transacted messages. this information is written into memory along with message data words. the message information word contains word count, message errors, and message type information. 1.2 bus controller features the s m mmit bus controller (sbc) is a powerful mil-std- 1553 bus controller developed to meet the requirements of multi-frame processing with low host overhead. user-defined decision making allows the sbc to operate autonomously from the host until a designated event or series of events has taken place.
s m mmit family - 2 1.2.1 multiple message processing the sbc architecture allows the chaining of multiple mil- std-1553 commands into major and minor frames depending on the application. this feature allows the host to structure message frames that perform independent tasks such as periodic data transfer, service requests, and bus diagnostics (initiate bit). the sbc uses a simple opcode scheme to control the command block flow. 1.2.2 message scheduling the sbc allows host entry of data to control the time between messages. this feature is useful when the bc has to perform periodic message transactions with multiple remote terminals. 1.2.3 polling the host instructs the sbc to interrogate the status word response of remote terminals to determine if any sbc action is required. the sbc can detect the assertion of status word bits and generate interrupts or branch to a new message frame. polling is useful if the application requires control of message frame flow as a function of remote terminal response. 1.2.4 automatic retry the sbc can automatically retry a message on busy, message error, or other status word bit response. if enabled, the sbc can retry up to four times, per command block, on the primary bus or alternate bus. 1.3 monitor terminal features the s m mmit monitor terminal (smt) is a full-featured mil- std-1553b bus monitor designed to monitor all or selected remote terminals on the bus. requiring little host intervention, the smt will monitor selected remote terminals until a pre- defined message count is reached. generation of an interrupt alerts the host that smt service is required. 1.3.1 message information each message transaction generates a message information word. this information helps determine message validity and remote terminal health. the message information word is stored in external memory along with message data words. 1.4 remote terminal/monitor terminal feature for those applications that require the smt to transfer or receive information, the s m mmit is configured as both a remote terminal (srt) and monitor (smt). this feature allows the smt to communicate on the bus as a rt, and monitor bus activity. configuration as both smt and srt precludes the smt from monitoring its own remote terminal address. 1.5 protocol definition for maximum flexibility, the s mmm it has been designed to operate in many different systems which use various protocols. specifically, two of the protocols that the s m mmit may interface are mil-std-1553a and mil-std-1553b. to meet these protocols, the s mmm it may be configured through an external pin or through control register bits. 1.6 s m mmit lxe/dxe & xte transceivers internal monolithic transceivers are complete transmitter and receiver pairs for mil-std-1553a and 1553b applications. the receiver section accepts biphase-modulated manchester ii bipolar data from mil-std-1553 data bus and produces ttl- level signal data at its internal rxout and rxout outputs. the transmitter section accepts biphase ttl-level signal data at its internal txin and txin inputs and produces mil-std- 1553 data signals. the transmitter?s output voltage is typically 10v p-p,ll for the s m mmit xte5 & dxe and 42v p-p,ll for the s m mmit xte15, xte12 & lxe. 1.7 s m mmit xte memory the s m mmit xte contains 512 kbits of internal memory for message processing. internal logic generates a rdy signal for the subsystem interface. the internal memory is memory mapped.
s m mmit family - 3 s m mmit f e a t u r e s r comprehensive mil-std-1553 dual redundant bus controller (bc), remote terminal (rt), and monitor terminal (mt) r mil-std-1553b, notice ii rt - internal command illegalization in the rt mode - 16-bit read/write time-tag with user-defined resolution - subaddress data buffering r simultaneous rt/mt mode of operation r flexible bc architecture designed to off-load the host computer - minor frame timing - efficient command block flow statements (branch, go to, call) - status word polling - programmable retries r programmable interrupt architecture with automatic interrupt logging available in all modes r autonomous operation in all three modes of operation - ideal for low cost remote terminals r built-in test capability r supports ieee standard 1149.1 (jtag) r radiation-hardened option available r flexible packaging offering: - 8 4- pin pingrid array (pga) (not available radhard) - 84-lead flatpack - 132-lead flatpack (not available radhard) r standard microcircuit drawing 5962-92118 available - qml q & v compliant figure 1. ut69151 s m mmit block diagram decoder decoder clock and reset logic built-in test data transfer logic interrupt control instruction memory boundary scan control master reset and clocks address/data and control signals interrupt outputs configuration control inputs status signals encoder bc controller rt controller mt controller register file (32 x 16) message buffer o u t p u t m u l t i p l e x o r a n d s e l f - t e s t w r a p - a r o u n d l o g i c channel a channel b
s m mmit family - 4 lxe/dxe f e a t u r e s r comprehensive mil-std-1553 dual redundant bus controller(bc), remote terminal (rt), and monitor terminal (mt) with integrated bus transceivers r mil-std-1553b, notice ii rt - internal command illegalization in the rt mode - 16-bit read/write time-tag with user-defined resolution - subaddress data buffering r simultaneous rt/mt mode of operation r flexible bc architecture designed to off-load the host computer - minor frame timing - efficient command block flow statements (branch, go to, call) - status word polling - programmable retries r programmable interrupt architecture with automatic interrupt logging available in all modes r autonomous operation in all three modes of operation - ideal for low cost remote terminals r built-in test capability r supports ieee standard 1149.1 (jtag) r flexible power supply configurations - +5-volt only operation - -15-volt and 5-volt operation - -12-volt and 5-volt operation r radiation-hardened option available r flexible packaging offering: - 96-pin pingrid array (pga) (not available radhard) - 100-lead flatpack - complete interface in 1.4 in 2 r standard microcircuit drawing 5962-94663 - qml q and v compliant transceiver cha cha transceiver chb chb s m mmit remote terminal address auto-init bus mode status jtag address data interface control figure 2. ut69151 s m mmit lxe/dxe block diagram interrupts
s m mmit family - 5 xte f e a t u r e s r comprehensive mil-std-1553 dual redundant bus controller (bc), remote terminal (rt), and monitor terminal (mt) with integrated bus transceivers, memory, and memory management unit (mmu) r mil-std-1553b, notice ii rt - internal command illegalization in the rt mode - 16-bit read/write time-tag with user-defined resolution - subaddress data buffering r simultaneous rt/mt mode of operation r flexible bc architecture designed to off-load the host computer - minor frame timing - efficient command block flow statements (branch, go to, call) - status word polling - programmable retries r programmable interrupt architecture with automatic interrupt logging available in all modes r autonomous operation in all three modes of operation - external initialization bus - ideal for low cost remote terminals r internal memory management unit (mmu) interfaces host subsystem to 512kbit sram - wait state and zero-wait state configurations r built-in test capability r supports ieee standard 1149.1 (jtag) r flexible power supply configurations - +5-volt only operation - -15-volt and 5-volt operation - -12-volt and 5-volt operation r flexible packaging offering: - 139-pin pingrid array (pga) - 140-lead flatpack - complete interface in 1.9 in 2 r standard microcircuit drawing 5962-94758 - qml q and v compliant transceiver cha cha transceiver chb chb s m mmit protocol handler mmu address data interface control remote terminal address memory mode status interrupts jtag figure 3. ut69151 s m mmit xte block diagram memory auto-init bus
s m mmit family - 3 s m mmit f e a t u r e s r comprehensive mil-std-1553 dual redundant bus controller (bc), remote terminal (rt), and monitor terminal (mt) r mil-std-1553b, notice ii rt - internal command illegalization in the rt mode - 16-bit read/write time-tag with user-defined resolution - subaddress data buffering r simultaneous rt/mt mode of operation r flexible bc architecture designed to off-load the host computer - minor frame timing - efficient command block flow statements (branch, go to, call) - status word polling - programmable retries r programmable interrupt architecture with automatic interrupt logging available in all modes r autonomous operation in all three modes of operation - ideal for low cost remote terminals r built-in test capability r supports ieee standard 1149.1 (jtag) r radiation-hardened option available r flexible packaging offering: - 8 4- pin pingrid array (pga) - 84-lead flatpack - 132-lead flatpack r standard microcircuit drawing 5962-92118 available - qml q & v compliant figure 1. ut69151 s m mmit block diagram decoder decoder clock and reset logic built-in test data transfer logic interrupt control instruction memory boundary scan control master reset and clocks address/data and control signals interrupt outputs configuration control inputs status signals encoder bc controller rt controller mt controller register file (32 x 16) message buffer o u t p u t m u l t i p l e x o r a n d s e l f - t e s t w r a p - a r o u n d l o g i c channel a channel b
s m mmit family - 4 lxe/dxe f e a t u r e s r comprehensive mil-std-1553 dual redundant bus controller(bc), remote terminal (rt), and monitor terminal (mt) with integrated bus transceivers r mil-std-1553b, notice ii rt - internal command illegalization in the rt mode - 16-bit read/write time-tag with user-defined resolution - subaddress data buffering r simultaneous rt/mt mode of operation r flexible bc architecture designed to off-load the host computer - minor frame timing - efficient command block flow statements (branch, go to, call) - status word polling - programmable retries r programmable interrupt architecture with automatic interrupt logging available in all modes r autonomous operation in all three modes of operation - ideal for low cost remote terminals r built-in test capability r supports ieee standard 1149.1 (jtag) r flexible power supply configurations - +5-volt only operation - -15-volt and 5-volt operation - -12-volt and 5-volt operation r radiation-hardened option available (lx version only) r flexible packaging offering: - 96-pin pingrid array (pga) - 100-lead flatpack - complete interface in 1.4 in 2 r standard microcircuit drawing 5962-94663 - qml q and v compliant transceiver cha cha transceiver chb chb s m mmit remote terminal address auto-init bus mode status jtag address data interface control figure 2. ut69151 s m mmit lxe/dxe block diagram interrupts
s m mmit family - 5 xte f e a t u r e s r comprehensive mil-std-1553 dual redundant bus controller (bc), remote terminal (rt), and monitor terminal (mt) with integrated bus transceivers, memory, and memory management unit (mmu) r mil-std-1553b, notice ii rt - internal command illegalization in the rt mode - 16-bit read/write time-tag with user-defined resolution - subaddress data buffering r simultaneous rt/mt mode of operation r flexible bc architecture designed to off-load the host computer - minor frame timing - efficient command block flow statements (branch, go to, call) - status word polling - programmable retries r programmable interrupt architecture with automatic interrupt logging available in all modes r autonomous operation in all three modes of operation - external initialization bus - ideal for low cost remote terminals r internal memory management unit (mmu) interfaces host subsystem to 512kbit sram - wait state and zero-wait state configurations r built-in test capability r supports ieee standard 1149.1 (jtag) r flexible power supply configurations - +5-volt only operation - -15-volt and 5-volt operation - -12-volt and 5-volt operation r flexible packaging offering: - 139-pin pingrid array (pga) - 140-lead flatpack - complete interface in 1.9 in 2 r standard microcircuit drawing 5962-94758 - qml q and v compliant transceiver cha cha transceiver chb chb s m mmit protocol handler mmu address data interface control remote terminal address memory mode status interrupts jtag figure 3. ut69151 s m mmit xte block diagram memory auto-init bus
6 s m mmit family 2.0 r e m o t e t e r m i n a l a r c h i t e c t u r e the s m mmit remote terminal (srt) is an interface device linking a mil-std-1553 serial data bus to a host microprocessor and/or subsystem. the srt?s mil-std-1553 interface includes encoding/decoding logic, error detection, command recognition, dma interface, control/configuration registers, clock, and reset logic. the following sections review the architecture and use. each section supplies information on the srt?s configuration and operation. 2.1 register descriptions the following list provides the bit descriptions of the 32 internal registers that control srt operation. all register bits are active high and reflect a logic zero condition (0000 hex) after master reset (except those reflecting input pins). note: reference section 9.1.2 for s m mmit xt 8-bit register address numbers. 2.1.1 control register (read/write) - register 0 this 16-bit register controls srt configuration. to make changes to the srt and this register, the stex bit (bit 15 of the contr ol register) must be logic zero. note: the user has 5 m s after teract active to stop execution. register number name register address 0 control register 0000 (hex) 1 operational status register 0001 (hex) 2 current command register 0002 (hex) 3 interrupt mask register 0003 (hex) 4 pending interrupt register 0004 (hex) 5 interrupt log list pointer register 0005 (hex) 6 bit word register 0006 (hex) 7 time-tag register 0007 (hex) 8 srt descriptor pointer register 0008 (hex) 9 1553 status word bits register 0009 (hex) 10-15 not applicable 000a to 000f (hex) 16-31 illegalization registers 0010 to 001f (hex) bit mnemonic description number 15 stex start execution. assertion of this bit initiates s mmm it operation. a control register write negating this bit inhibits s mmm it operation. a remote terminal address parity error prevents srt operation regardless of the logical state of this bit. if a rt address parity error exists, bit 3 of register 1 will be set low and bit 2 of register 1 will be set high. 14 sbit start bit. assertion of this bit places the s mmm it into the built-in test routine. the bit test has a fault coverage of 93.4%. if the s mmm it has been started, the host must halt the device in order to place the s mmm it into the built-in test routine (stex = 0) (see section 8.0 for additional information). note: if start bit (sbit) and start execution (stex) are both set on one register write, bit has priority.
7 s m mmit family 13 srst software reset. assertion of this bit immediately places the s mmm it into a software reset. the software reset (which takes 5 m s to execute), like mrst , clears all internal logic. note: during auto-initialization this bit should not be loaded with a logic one. srst will only function after readyb is asserted. 12 chaen channel a enable. setting this bit enables channel a operation. if negated, the srt does not recognize commands received over channel a. 11 chben channel b enable. setting this bit enables channel b operation. if negated, the srt does not recognize commands received over channel b. 10 etce external timer clock enable. assertion of this bit to a logic one allows the external timer clock input to supply stimulus to the internal time-tag counter. refer to section 2.1.8 for additional information. note: the user can only change the clock frequency before starting the device (i.e., setting bit 15 of register 0 to a logic one). 9-7 -- see section 5, enhanced s m mmit family operation for additional information. 6 bufr buffer mode enable. assertion of this bit enables the buffer mode of operation. for more detailed information on this feature refer to sections 9.1.5 or 9.2.3. 5 n/a not applicable. 4 bcen broadcast enable. assertion of this bit enables the srt broadcast option. negation of this bit enables remote terminal address 31 as a unique remote terminal address. 3 dynbc dynamic bus control acceptance. this bit controls the srt?s ability to accept the dynamic bus control mode code. assertion of this bit allows the srt to respond to a dynamic bus control mode code with status word bit 18 set to a logic one. negation of this bit prevents the assertion of status word bit 18 upon reception of the dynamic mode code. 2 ppen ping-pong enable. assertion of this bit enables the ping-pong buffer feature of the srt and disables the message indexing feature. negation of this bit disables the ping-pong feature and enables the message indexing feature. see section 5, enhanced s m mmit family operation for additional information. 1 inten interrupt log enable. assertion of this bit enables the s mmm it interrupt logging feature. negation of this bit prevents the logging of interrupts. 0 xmtsw transmit status word. assertion of this bit allows the srt to automatically execute the transmit status word mode code when configured for mil- std-1553a mode operation. refer to section 2.9 for additional information. bit mnemonic description number bit mnemonic description number
8 s m mmit family 2.1.2 operational status register (read/write) - register 1 this register reflects pertinent status information for the srt and is not reset to 0000 (hex) on mrst . instead, the register reflects the actual stimulus applied to input pins rta(4:0), rtpty, msel(1:0), a/ b std, and lock . assertion of the lock input prevents the modification of the remote terminal address, mode selects, and a or b standard. in this case, a write to this register?s mos t significant nine bits is meaningless. if lock is negated, a read of this register reflects the information written into this register?s most significant nine bits. note: to make changes to the srt and this register, the stex bit (bit 15 in register 0) must be logic zero . bit mnemonic description number 15 rta4 terminal address bit 4. this bit is the most significant bit of the remote terminal address. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 14 rta3 terminal address bit 3. this bit is bit 3 of the remote terminal address. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 13 rta2 terminal address bit 2. this bit is bit 2 of the remote terminal address. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 12 rta1 terminal address bit 1. this bit is bit 1 of the remote terminal address. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 11 rta0 terminal address bit 0. this bit is the least significant bit of the remote terminal address. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 10 rtpty terminal address parity bit. this bit is appended to the remote terminal address bus (rta(4:0)) to supply odd parity. the srt requires odd parity for proper operation. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 9 msel(1) mode select 1. in conjunction with msel0, this bit determines the s mmm it mode of operation. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. 8 msel(0) mode select 0. in conjunction with msel1, this bit determines the s mmm it mode of operation. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. msel(1) msel(0) mode of operation 0 0 sbc 0 1 srt 1 0 smt 1 1 smt/srt 7 a/ b std military standard 1553a or 1553b standard. this bit determines whether the srt will be set to operate under mil-std-1553a or b. assertion of this bit enables the xmtsw bit (bit 0 of the control register). negation of this bit automatically allows the srt to operate under the mil-std-1553b protocol. this bit is latched on the rising edge of mrst and is a read only bit if the lock pin is active. see section 2.9 for further definition. 6 lock lock pin. this read-only bit reflects the inverted state of input pin lock and is latched on the rising edge of mrst . 5 autoen autoen pin. this read-only bit reflects the inverted state of input pin autoen . assertion of this input enables srt auto-initialization. 4 ssysf ssysf pin. this read-only bit reflects the inverted state of the input pin ssysf .
9 s m mmit family note: remote terminal address and parity checked on start of execution. 2.1.3 current command register (read-only) - register 2 this 16-bit register contains the last valid command processed by the srt. 3 ex s mmm it executing. this read-only bit indicates whether the srt is presently executing or whether it is idle. a logic one indicates that the s mmm it is executing; logic zero indicates that the s mmm it is idle. 2 tapf terminal address parity fail. this bit indicates the observance of a terminal address parity error. the srt checks for odd parity. this read only bit reflects the parity of operational status register bits 15-10, and is latched on the rising edge of mrst . 1 ready ready pin. this read-only bit reflects the inverted state of the output pin ready and is cleared on reset. 0 teract teract pin. assertion of this bit indicates that the srt is presently processing a message. this read only bit reflects the inverted state of output pin teract and is cleared on reset. bit mnemonic description number 15 to 0 cc15-cc0 current command bits. this register contains the last valid command received by the srt. this register is valid 13 m s after teract is active. (bit 15 msb - bit 0 lsb). bit mnemonic description number
10 s m mmit family 2.1.4 interrupt mask register (read/write) - register 3 the srt interrupt architecture allows for the masking of all interrupts. an interrupt is masked if the corresponding bit of this register is set to logic zero. this feature allows the host or subsystem to temporarily disable the service of interrupts. while masked, interrupt activity does not occur. the unmasking of an interrupt after the event occurs does not generate an interrupt for that event. 2.1.5 pending interrupt register (read-only) - register 4 the pending interrupt register contains information that identifies events that generate interrupts. the assertion of any bit in this register asserts an output pin, msg_int or yf_int (three clock cycles). writing to the most significant 4 bits of this register generates a yf_int . . bit mnemonic description number 15 dmaf dma fail interrupt 14 wrapf wrap fail interrupt 13 tapf terminal address parity fail interrupt 12 bitf bit fail interrupt 11 merr message error interrupt 10 subad subaddress accessed interrupt 9 bdrcv broadcast command received interrupt 8 ixeq0 index equal zero interrupt 7 illcmd illegal command interrupt 6-0 n/a not applicable+
11 s m mmit family bit mnemonic description number 15 dmaf dma fail interrupt. once the s mmm it issues the dmar signal, an internal timer starts. if all dma activity (which includes dmar to dmag , and all wait states) is not completed by the time the counter decrements to zero, the interrupt is generated. in the srt mode, the yf_int interrupt is generated (if not masked), current command processing ends, and the srt will remain on-line. current cycle terminated, bus released. 14 wrapf wrap fail interrupt. the srt automatically compares the transmitted word (encoder word) to the reflected decoder word via the continuous loop-back feature. if the encoder word and reflected word do not match, the wrapf bit is asserted in the bit word register and a yf_int interrupt is generated (if not masked). the loop-back path is via the mil- std-1553 bus transceiver. 13 tapf terminal address parity fail interrupt. this bit reflects the outcome of the remote terminal address parity check. a logic one indicates a parity failure. when a parity error occurs, the srt does not begin operation (stex bit forced to logic zero), channel a and b do not enable, the tapf bit is asserted here and in the bit word register, and a yf_int interrupt is generated (if not masked). 12 bitf bit fail interrupt. assertion of this bit indicates a bit failure. status word bit 19 is automatically set to a logic one when a bit failure occurs. if a bit fails, the bitf bit is asserted here and in the bit word register, and a yf_int interrupt is generated (if not masked). operation continues. 11 merr message error interrupt. assertion of this bit indicates that a message error condition exists. the srt can detect manchester errors, sync-field, word count errors (too many or too few), mil-std-1553 word parity errors, bit count errors (too many or too few), and protocol errors. if not masked, this bit is always set when the srt asserts bit 9 of the status word (e.g., illegal commands, invalid data word, etc.). msg_int interrupt generated (if not masked). 10 subad subaddress accessed interrupt. assertion of this bit indicates a pre-selected subaddress has transacted a message. to determine the exact subaddress, the host interrogates the interrupt log iaw. msg_int interrupt generated (if not masked). 9 bdrcv broadcast command received interrupt. this bit is set to a logic one to indicate the srt?s receipt of a valid broadcast command. the srt suppresses status word transmission. msg_int interrupt generated (if not masked). 8 ixeq0 index equal zero interrupt. the srt asserts this bit to indicate the completion of a pre- defined number of commands by the srt. upon assertion of this interrupt, the host or subsystem updates the subaddress descriptor to prevent the potential loss of data. msg_int interrupt generated (if not masked). 7 illcmd illegal command interrupt. this bit is set to a logic one to indicate the reception of an illegal command by the srt. upon receipt of this command, the srt responds with a status word only; bit 9 of the status word is set to a logic one. msg_int interrupt generated (if not masked). 6-0 n/a not applicable. note: the user must read or write a s m mmit register after reading the pending register to invoke the automatic clear of the pending interrupt register. for example, a subaddress access interrupt results in a pending interrupt register of 0400 16 . a read of the pending interrupt register returns a value of 0400 16 . a subsequent read of the interrupt mask register (i.e., register 3), followed by a pending interrupt register read returns a value of 0000 16 . the intervening read of the interrupt mask register clears the pending interrupt register at the end of the interrupt mask register read.
12 s m mmit family 2.1.6 interrupt log list pointer register (read/write) - register 5 the interrupt log list pointer indicates the starting address of the interrupt log list. the interrupt log list is a 32 word rin g- buffer that contains information pertinent to the service of interrupts. the s mmm it architecture requires the location of the interrupt log list on a 32-word boundary. the most significant 11 bits of this register designate the location of the interrupt log list w ithin a 64k memory space. the lower 5 bits of this register should be initialized to a logic zero. the s mmm it controls the lower 5 bits to implement the ring-buffer architecture. the host or subsystem reads this register to determine the location and number of int errupts within the interrupt log list (least significant 5 bits). note: bits 15-5 indicate the starting base address while bits 4-0 indicate the ring location of the interrupt log list. see sect ion 6.0 for a description of the interrupt architecture. 2.1.7 bit word register (read/write) - register 6 this register contains information on the srt?s current health. the srt transmits the contents of this register upon reception o f a transmit bit word mode code. the lower 8 bits of this register are user-defined. bit mnemonic description number 15-0 inta(15:0) interrupt log list pointer bits. (bit 15 msb - bit 0 lsb). bit mnemonic description number 15 dmaf dma fail. this bit is set if all dma activity is not completed between the time dmar asserts and when the timer decrements to zero. the dma activity includes dmar to dmag and all wait states. in the event of a dma failure, current message processing terminates; remote terminal waits for next 1553 message. 14 wrapf wrap fail. the srt automatically compares the transmitted word (encoder word) to the reflected decoder word via the continuous loop-back feature. if the encoder word and reflected word do not match, the wrapf bit asserts and a yf_int interrupt is generated (if not masked). the loop-back path is via the mil-std-1553 bus transceiver. a wrap failure does not result in the terminal flag bit being set to a logical one. message processing continues. 13 tapf terminal address parity fail. this bit reflects the outcome of the remote terminal address parity check. a logic one indicates a parity failure. when a parity error occurs the srt does not begin operation (stex bit forced to a logic zero), channel a and b do not enable, and a yf_int interrupt is generated (if not masked). 12 bitf bit fail. assertion of this bit indicates a bit failure. bits 11 through 8 should be interrogated to determine the specific failure. status word bit 19 is automatically set to a logic one when a bit failure occurs. if a bit fails, the bitf bit is asserted, and a yf_int interrupt is generated (if not masked). operation continues. 11 chaf channel a fail. assertion of this bit indicates a bit test failure in channel a. 10 chbf channel b fail. assertion of this bit indicates a bit test failure in channel b. 9 msbf/udb memory test fail. most significant memory byte failure (s m mmit xt). user-defined bits (s m mmit & s m mmit lx/dx). 8 lsbf/udb memory test fail. least significant memory byte failure (s m mmit xt). user-defined bits (s m mmit & s m mmit lx/dx). 7-0 udb(7:0) user-defined bits.
13 s m mmit family 2.1.8 time-tag register (read/write) - register 7 the time-tag register reflects the state of a 16-bit free running counter. the resolution of this counter is user-defined via in put tclk or fixed at 64 m s/bit. the time-tag counter is automatically reset when the srt receives a valid synchronize without data mode code. the srt automatically loads the time-tag counter with the data associated with reception of a valid synchronize with data mode code. the time-tag counter begins operation on the rising edge of mrst or within 64 m s; after the receipt of a valid mode code, reset remote terminal, or sync with/without data. when the srt is halted (stex = 0), the time-tag continues to run.time-tag value is captured upon command word-validation. 2.1.9 remote terminal descriptor pointer register (read/write) - register 8 the srt accesses a block of external memory to gain information on how to process a valid command. each subaddress and mode code has a block of memory reserved for this task. located contiguously in memory, these reserved memory locations are called a descriptor space. the remote terminal descriptor pointer register contains an address that points to the top of this memory spac e. the srt uses the t/ r bit, subaddress/mode code field, and mode code to select one block within the descriptor table for message processing. the remote terminal descriptor pointer register is static during message processing. bit mnemonic description number 15-0 tt(15:0) time-tag counter bits. (bit 15 msb - bit 0 lsb) bit mnemonic description number 15-0 rtda(15:0) remote terminal descriptor address bits. (bit 15 msb - bit 0 lsb)
14 s m mmit family 2.1.10 1553 status word bits register (read/write) - register 9 the host or subsystem accesses this register to control the outgoing mil-std-1553 status word. the host or subsystem controls the instrumentation, busy, terminal flag, service request, and subsystem flag by writing to bits 9 through 0 of this register. t he srt?s status word response reflects assertion of these bit(s) until negated by the host or subsystem unless the immediate clear function is enabled. the immediate clear function automatically clears these bits after being transmitted in a status word. the immediate clear function does not affect the operation of the transmit status word and transmit last command word mode codes. transaction of a legal valid command with the ins bit set to a logic one and the immediate clear function enabled, result s in the transmission of a status word with bit 10 asserted. if the ensuing command is a transmit status word or last command mode code, bit 10 of the outgoing status word remains a logic one. for mil-std-1553b applications, the register is as follows: bit number mnemonic description 15 imclr immediate clear function. assertion of this bit enables the immediate clear function (imf) of the srt. enabling the imf results in the clearing of the ins, busy, tf, srq, and/or subf bit immediately after a message is completed. this function is enabled by asserting this bit when asserting bit(s) ins, busy, tf, srq, and/or ssysf. this bit should be used consistently since once set, it will remain set, and once cleared, it will remain cleared. 14-10 n/a not applicable. 9 ins instrumentation bit. this bit asserts the instrumentation bit of the mil-std-1553b status word. (bit 10 of the status word). 8 srq service request bit. this bit asserts the service request bit of the mil-std-1553b status word. (bit 11 of the status word). 7-4 n/a not applicable. 3 busy busy bit. assertion of this bit is reflected in the outgoing mil-std-1553b status word. assertion of this bit prevents memory accesses. (bit 16 of the status word). 2 ssysf subsystem flag bit. this bit asserts the subsystem flag bit of the mil-std-1553b status word and may also be set with the ssysf input pin. (bit 17 of the status word). 1 n/a not applicable. 0 tf terminal flag. assertion of this bit is reflected in the outgoing mil-std-1553b status word. the srt automatically asserts this bit if a bit failure occurs. inhibit terminal flag mode code prevents the assertion by the host or subsystem. override inhibit terminal flag mode code re-establishes the terminal flag option (bit 19 of the status word).
15 s m mmit family for mil-std-1553a applications, the register is as follows: bit number mnemonic description 15 imclr immediate clear function. assertion of this bit enables the immediate clear function (imf) of the srt. enabling the imf results in the clearing of the bit times 10-19 immediately after a status word is transmitted. this function is enabled by asserting this bit when asserting bit times 10-19. this bit should be used consistently since once set, it will remain set, and once cleared, it will remain cleared. 14-10 n/a not applicable. 9 sb10 status bit time 10. 8 sb11 status bit time 11. 7 sb12 status bit time 12. 6 sb13 status bit time 13. 5 sb14 status bit time 14. 4 sb15 status bit time 15. 3 sb16 status bit time 16. 2 sb17 status bit time 17. 1 sb18 status bit time 18. 0 sb19 status bit time 19.
16 s m mmit family 2.1.11 illegalization registers the 16 registers are divided into 8 blocks, 2 registers per block (see table 1). table 1. illegalization register blocks the blocks correspond to the following types of commands. register address 0010 (hex) and 0011 (hex) illegalize receive commands to 32 subaddresses. the most significant bit of register 0010 (hex) controls the illegalization of subaddress 01111. the least s ignificant bit controls subaddress 00000. register 0011 (hex) controls illegalization of subaddresses 10000 through 11111. the least signif icant bit relates to subaddress 10000; the most significant bit relates to subaddress 11111. transmit commands and broadcast commands (both receive and transmit) use the same encoding scheme as receive subaddress illegalization. registers 18 (hex) through 1f (hex) control the illegalization of mode codes. register 18 governs the illegalization of receive mode codes (t/ r bit = 0) 00000 through 01111 and register 19 mode codes 10000 through 11111. register blocks transmit mode code (t/ r bit = 1), broadcast receive mode codes, and broadcast transmit mode codes use the same decode scheme as receive mode codes. table 2 shows the illegalization register map. for each block, the numbers shown in the column under each bit number identifies the specific subaddress or mode code (in hex) that the register bit illegalizes (logical 0 = legal, logical 1 = illegal). block name address (hex) receive 0010 and 0011 transmit 0012 and 0013 broadcast receive 0014 and 0015 broadcast transmit (automatically illegalized) 0016 and 0017 mode code receive 0018 and 0019 mode code transmit 001a and 001b broadcast mode code receive 001c and 001d broadcast mode code transmit 001e and 001f
17 s m mmit family table 2. illegalization register map notes: 1. brd = broadcast. 2. mode = mode code. 3. xx= automatically illegalized by srt. 4. yy= automatically illegalized by srt in 1553b only. 5. zz= automatically illegalized by srt in 1553b and 1553a if xmtsw is enabled. 6. ww = automatically illegalized in 1553a. 7. uu = automatically illegalized in 1553a if xmtsw enabled. name register number bit number 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 receive 16 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 17 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 transmit 18 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 19 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 brd receive 20 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 21 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 brd transmit 22 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx 23 xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx mode receive 24 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 25 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 mode transmit 26 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 02 01 00 27 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 mode brd receive 28 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 uu 01 ww 29 1f 1e 1d 1c 1b 1a 19 18 17 16 15 14 13 12 11 10 mode brd transmit 30 0f 0e 0d 0c 0b 0a 09 08 07 06 05 04 03 zz 01 xx 31 yy yy yy yy yy yy yy yy yy yy yy yy yy yy yy yy
18 s m mmit family 2.2 descriptor block to process messages, the srt uses data supplied in the internal registers with data stored in external memory. the srt accesses a four word descriptor block stored in external memory. the descriptor block is accessed at the beginning and end of command processing. multiple descriptor blocks are sequentially entered into memory to form a descriptor table. the following paragraphs discuss the descriptor block in detail. the host or subsystem controlling the srt allocates 512 consecutive memory spaces for the subaddress and mode code descriptor table. the top of the descriptor table can reside at any address location. defined and entered into memory by the host, the srt is linked to the descriptor table via the descriptor address register contents (see figures 4a and 4b). each descriptor block contains a control word, data pointer a, data pointer b, and broadcast data pointer. each subaddress and mode code is assigned a descriptor for receive and transmit commands (t/ r bit equal zero or one). control word information allows the srt to generate interrupts, buffer messages, and control message processing. for a receive command, the data pointer is read to determine the top of the data buffer. the srt stores data sequentially from the top of data buffer plus two locations (e.g., 0100, 0101, 0102, 0103, etc.). when processing a transmit command, the data pointer is read to determine where data words are retrieved. the srt retrieves data words sequentially from the address the data pointer designates plus two address locations. the broadcast data pointer allows for separate storage of non- broadcast data from broadcast data per mil-std-1553b notice ii. the host or subsystem enables or disables this feature via the control word?s least significant bit. when disabled, the non- broadcast and broadcast data is stored via data list pointer a or b. for transmit commands, the broadcast data pointer is not used. the srt does not transmit any information on the receipt of a broadcast transmit command. the srt reads the descriptor block during command processing (i.e., after assertion of teract ). the srt arbitrates for the memory bus. after receiving control of the bus, the srt reads the control word and three data pointers. the srt then surrenders control of the bus back to the bus master (i.e., negates dmack ). the srt then begins the acquisition of data words for either transmission or storage. after transmission or reception, the srt begins post- processing. command post-processing begins with arbitration for the memory bus. the srt performs a dma burst during post-processing. an optional interrupt log entry is performed after a descriptor update. during the descriptor update, the srt modifies the control word index field and bits 4, 2, and 1, if required. the srt updates data pointer a if no message errors occurred during the message transaction. reception of a broadcast command, with no message errors, results in the update of the broadcast data pointer. neither data pointer a, b or broadcast is updated if the srt has the ping-pong mode of operation enabled. see section 5, enhanced s m mmit family operation for additional information. subaddress/mode code address equation subaddress descriptor address register contents + [(sa# x 4) + 0] subaddress descriptor address register contents + [(sa# x 4) + 128] descriptor address register contents + [(mc# x 4) + 256] descriptor address register contents + [(mc# x 4) + 384] figure 4a. descriptor table (16-bit data bus) descriptors mode codes mode codes 0 0 1 1 t/r
19 s m mmit family receive receive ? ? ? receive receive transmit transmit subaddress #0 subaddress #1 subaddress #30 subaddress #31 subaddress #0 subaddress #1 transmit transmit ? ? ? subaddress #30 subaddress #31 relative address 0000 (hex) relative address 00fc (hex) receive receive ? ? ? receive receive transmit transmit mode code #0 mode code #1 mode code #30 mode code #31 mode code #0 mode code #1 transmit transmit ? ? ? mode code #30 mode code #31 relative address 0100 (hex) relative address 01fc (hex) figure 4b. descriptor table (16-bit data bus) subaddress/mode code address equation subaddress descriptor address register contents + [(sa# x 8) + 0] subaddress descriptor address register contents + [(sa# x 8) + 256] descriptor address register contents + [(mc# x 8) + 512] descriptor address register contents + [(mc# x 8) + 768] figure 4c. descriptor table (8-bit data bus) descriptors mode codes mode codes 0 0 1 1 t/r
20 s m mmit family receive receive ? ? ? receive receive transmit transmit subaddress #0 subaddress #1 subaddress #30 subaddress #31 subaddress #0 subaddress #1 transmit transmit ? ? ? subaddress #30 subaddress #31 relative address 0000 (hex) relative address 01f8 (hex) receive receive ? ? ? receive receive transmit transmit mode code #0 mode code #1 mode code #30 mode code #31 mode code #0 mode code #1 transmit transmit ? ? ? mode code #30 mode code #31 relative address 0200 (hex) relative address 03f8 (hex) figure 4d. descriptor table (8-bit data bus)
21 s m mmit family 2.2.1 receive control word the following bits describe the receive subaddress descriptor control word. information contained in this word assists the srt i n message processing. the descriptor control word is initialized by the host or subsystem and updated by the srt during command post-processing. bit mnemonic description number 15-8 indx index field. these bits define multiple message buffer length. the host or subsystem uses this field to instruct the srt to buffer ?n? messages. ?n? can range from 0 (00 hex) to 255 (ff hex). if buffer ping-ponging is enabled, the indx field is ?don?t care? (i.e., does not contain applicable information). during ping-pong mode operation, initialize the index field to 00 (hex). the srt does not perform multiple message buffering in the ping- pong mode of operation. the index decrements each time a complete message is transacted (no message errors). the index does not decrement if the subaddress is illegalized. the srt can generate an interrupt when the index field transitions from one to zero (see bit 7). 7 intx interrupt index equals zero. assertion of this bit enables the generation of an interrupt when the index field transitions from one to zero. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 6 iwa interrupt when accessed. assertion of this bit enables the generation of an interrupt when the subaddress receives a valid command. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 5 ibrd interrupt broadcast received. assertion of this bit enables the generation of an interrupt when the subaddress receives a valid broadcast command. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 4 bac block accessed. the subsystem or host initializes this bit to zero; the srt overwrites the zero with a logic one upon completion of message processing. after interrogating this bit, the host resets this bit to zero to observe further accesses. 3 n/a not applicable. 2 a/ b buffer a/ b . indicates the last buffer accessed when buffer ping-pong is enabled. during initialization, the host designates the first buffer used by asserting or negating this bit. a logic one indicates buffer a; a logic zero indicates buffer b. this bit is a ?don?t care? if buffer ping-ponging is not enabled. 1 brd broadcast received. assertion of this bit indicates the reception of a valid broadcast command. 0 nii notice ii. assertion of this bit enables the use of the broadcast data pointer as a buffer for broadcast command information. when negated, broadcast information is stored in the same buffer as non-broadcast information.
22 s m mmit family 2.2.2 transmit control word the following bits describe the transmit subaddress descriptor control word. information contained in this word assists the srt in message processing. the descriptor control word is initialized by the host or subsystem and updated by the srt during command post-processing. bit mnemonic description number 15-7 n/a not applicable. 6 iwa interrupt when accessed. assertion of this bit enables the generation of an interrupt when the subaddress receives a valid command. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 5 n/a not applicable. 4 bac block accessed. the subsystem or host initializes this bit to zero, the srt overwrites the zero with a logic one upon completion of message processing. after interrogation, the host should reset this bit to zero to observe further accesses. 3 n/a not applicable. 2 a/ b buffer a/ b . indicates the data pointer to access when buffer ping-pong is enabled. during initialization, the host designates the first buffer used by asserting or negating this bit. a logic one indicates buffer a; a logic zero indicates buffer b. this bit is a ?don?t care? if buffer ping-ponging is not enabled. 1 brd broadcast received. assertion of this bit indicates the reception of a broadcast command. 0 n/a not applicable.
23 s m mmit family 2.2.3 mode code receive control word the following bits describe the receive mode code descriptor control word. information contained in this word assists the srt in message processing. the descriptor control word is initialized by the host or subsystem and updated by the srt during command post-processing. note: in mil-std-1553a, all mode codes are without data, and the t/ r bit is ignored. see section 2.9 for the mil-std-1553a operation. bit mnemonic description number 15-8 indx index field. these bits define message buffer length. the host or subsystem uses this field to instruct the srt to buffer ?n? messages. ?n? can range from 0 (00 hex) to 256 (ff hex). if buffer ping-ponging is enabled, the indx field is ?don?t care? (i.e., does not contain applicable information). the srt does not perform message buffering in the ping- pong mode of operation. the index decrements each time a complete message is transacted (no message errors). the index does not decrement if the mode code is illegalized. the srt can generate an interrupt when the index field transitions from one to zero (see bit 7). 7 intx interrupt index equals zero. assertion of this bit enables the generation of an interrupt when the index field transitions from one to zero. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 6 iwa interrupt when accessed. assertion of this bit enables the generation of an interrupt when mode code command is received. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 5 ibrd interrupt broadcast received. assertion of this bit enables the generation of an interrupt when a valid broadcast mode code command is received. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 4 bac block accessed. the subsystem or host initializes this bit to zero; the srt overwrites the zero with a logic one upon completion of message processing. after interrogating this bit, the host resets this bit to zero to observe further accesses. 3 n/a not applicable. 2 a/ b buffer a/ b . indicates the last buffer accessed when buffer ping-pong is enabled. during initialization, the host designates the first buffer used by asserting or negating this bit. a logic one indicates buffer a; logic zero indicates buffer b. this bit is a ?don?t care? if buffer ping-ponging is not enabled. 1 brd broadcast received. assertion of this bit indicates the reception of a valid broadcast command. 0 nii notice ii. asserting this bit enables the use of the broadcast data pointer as a buffer for broadcast command information. when negated, broadcast information is stored in the same buffer as non-broadcast information.
24 s m mmit family 2.2.4 mode code transmit control word the following bits describe the transmit mode code descriptor control word. information contained in this word assists the srt in message processing. the descriptor control word is initialized by the host or subsystem and updated by the srt during command post-processing. note: in mil-std-1553a, all mode codes are without data, and the t/ r bit is ignored. see section 2.9 for the mil-std-1553a operation. bit mnemonic description number 15-7 n/a not applicable. 6 iwa interrupt when accessed. assertion of this bit enables the generation of an interrupt when mode code command is received. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 5 ibrd interrupt broadcast received. assertion of this bit enables the generation of an interrupt when a valid broadcast mode code is received. the interrupt is entered into the pending interrupt register if not masked in the mask register. output pin msg_int asserts after message processing. 4 bac block accessed. the subsystem or host initializes this bit to zero; the srt overwrites the zero with a logic one upon completion of message processing. after interrogating this bit, the host resets this bit to zero to observe further accesses. 3 n/a not applicable. 2 a/ b buffer a/ b . this bit indicates the last buffer accessed when buffer ping-pong is enabled. during initialization, the host designates the first buffer used by asserting or negating this bit. a logic one indicates buffer a; a logic zero indicates buffer b. this bit is a ?don?t care? if buffer ping-ponging is not enabled. 1 brd broadcast received. assertion of this bit indicates the reception of a broadcast command. 0 n/a not applicable.
25 s m mmit family 2.2.5 data pointer a and b data pointer a and b contain address information for the retrieval and storage of message data words. in the index mode of opera tion, the srt reads data pointer a to determine the location of data for retrieval or storage. the srt uses the data pointer to initia lize an internal counter; the counter increments after each data word. for a receive command, the srt stores the incoming data word sequentially into memory. as part of command post-processing, the srt writes a new data pointer into the descriptor block. the srt continues to update the data pointer until the control word index field decrements to zero. an example is shown in figure 5. note: the index feature is not applicable for transmit commands (i.e., t/ r bit = 1). for ping-pong buffer operation, the host uses either data pointer a or data pointer b. the srt determines which pointer to acces s via the state of control word bit 2. the srt retrieves or stores data words from the address contained in the data pointer, auto matically incrementing the data pointer as data words are received. the data pointer is never updated as part of command post-processing i n the ping-pong mode of operation. see figures 6 and 7. 2.2.6 broadcast data pointer the following bits describe the receive subaddress/mode code descriptor broadcast data pointer. this word contains the address for the message information word, time-tag word, and data words associated with a broadcast command. the srt automatically increments this data pointer during command post-processing, if ping-pong operation disabled. 2.3 data structures the following sections discuss the data structures that result from command processing. for each complete message processed, the srt generates a message information word and time-tag word. these words aid the host or subsystem in further message processing. the message information word contains word count, message type, and message error information. the time-tag word is a 16-bit word containing the command validity time. the time-tag word data comes from the srt?s internal time-tag counter. see section 5, enhanced family s m mmit operation for additional data structure information bit mnemonic description number 15-0 dp(15:0) data pointer bits. the second and third words of the descriptor block contain the data buffer location. the srt accesses either data pointer a or data pointer b depending on the state of control word bit 2 during ping-pong operation. for index operation, the srt accesses only data pointer a. the srt updates data pointer a after message processing is complete and the index field is not equal to zero and ping-pong operation disabled. bit 15 is the most significant bit; bit 0 is the least significant bit. bit mnemonic description number 15-0 bp(15:0) broadcast data pointer. the fourth word of the descriptor block contains the broadcast data buffer location. this pointer can reside anywhere inside of a 64k data space. the srt accesses this pointer when control word bit 0 is a logic one and broadcast is enabled. bit 15 is the most significant bit; bit 0 is the least significant bit. note: if ping-pong is enabled, this pointer does not update. note: when the broadcast command is followed by a transmit last command or transmit status word mode code, the srt transmits a status word with bit 15 of the status word set to a logic one. the broadcast bit is cleared by reception of the next valid non-broadcast command.
26 s m mmit family figure 5. non-broadcast receive message indexing 0100 (hex) 0101 (hex) 0102 (hex) 0103 (hex) 0104 (hex) 0105 (hex) 0106 (hex) 0107 (hex) 0108 (hex) 0109 (hex) 010a (hex) 010b (hex) 010c (hex) 010d (hex) index equals two index decrements to one index equals one index decrements to zero (interrupt generated if enabled) index equals zero index remains zero (data pointer a = 109) message info word time-tag data word #1 data word #2 data word #3 message info word time-tag data word #1 data word #2 message info word time-tag data word #1 data word #2 data word #3 command #1 receive three words command #2 receive two words command #3 receive three words control word data pointer a data pointer b broadcast receive subaddress #1 descriptor block index field contents: 02xx (hex) data pointer a: 0100 (hex) data pointer b: xxxx (hex) broadcast data pointer: xxxx (hex) note: x = ?don?t care?
27 s m mmit family figure 6. srt descriptor block (receive) control word data pointer a data pointer b broadcast data pointer data buffer a data buffer b broadcast message message information word time-tag n - data words control word data pointer a data pointer b xxxx (hex) data buffer a data buffer b message message information word time-tag n - data words figure 7. srt descriptor block (transmit)
28 s m mmit family 2.3.1 subaddress receive data for receive commands, the srt stores data words plus two additional words. the srt adds a receive information word and time- tag word to each receive command data packet. the srt places the receive information word and time-tag word ahead of the data words associated with a receive command (see figures 5, 6 and 7). when message errors occur, the srt enters the receive information word, and time-tag word. once a message error condition is observed, all data words are considered invalid. data storage occurs at the memory location pointed to by the data pointer plus two locations. 2.3.1.1 receive information (info) word the following bits describe the receive information word contents. 2.3.2 subaddress transmit data the host or subsystem is responsible for organization of the data packet (i.e., n data words) into memory and establishing the applicable data pointer. the host or subsystem allocates two memory locations at the top of the data packet for the storage of t he transmit information word and time-tag word. an example transmit data structure for three words is shown below. data pointer a -----> 0100 (hex) xxxx ;reserved for transmit info word equals 0100 (hex) 0101 (hex) xxxx ;reserved for time-tag word 0102 (hex) ffff ;data word 0103 (hex) ffff ;data word 0104 (hex) ffff ;data word note: data pointer a points to the top of the data structure not to the top of the data words. bit mnemonic description number 15-11 wc(4:0) word count bits. these five bits contain word count information extracted from the transmit command word bits 15 to 19. 10 n/a not applicable. 9 cha/ b channel a/ b . assertion of this bit indicates that the message was received on channel a. conversely, if this bit is set to logic zero, the message was received on channel b. 8 rtrt remote terminal to remote terminal transfer. the command processed was a rt-to-rt transfer. 7 me message error. assertion of this bit indicates a message error condition was observed during processing. see bits 0 to 4 for details. 6-5 n/a not applicable. 4 ill illegal command received. assertion of this bit indicates the command received was an illegal command. 3 to time-out error. assertion of this bit indicates the srt did not receive the proper number of data words, i.e., the number of data words received was less than the word count specified in the command word. 2 ovr overrun error. assertion of this bit indicates the srt received a word when none was expected or the number of data words received was greater than expected. 1 prty parity error. assertion of this bit indicates the srt observed a parity error in the incoming data words. 0 man manchester error. assertion of this bit indicates the srt observed a manchester error in the incoming data words.
29 s m mmit family 2.3.2.1 transmit information (info) word the following bits describe the transmit information word contents. 2.3.3 mode code data the transmit and receive data structures for mode codes are similar to those for subaddress. the receive data structure contains an information word, time-tag word, and message data word. all receive mode codes with data have one associated data word. data storage occurs at the memory location pointed to by the data pointer plus two locations. reception of the synchronize with data mode code automatically loads the time-tag counter and stores the data word at the address defined by the data pointer plus two locations. the transmit mode code data structure contains an information word, time-tag word, and associated data word. the subsystem or host is responsible for linking the srt data pointer to the data (e.g., transmit vector word). for mode codes with internally ge nerated data words (e.g., transmit bit word, transmit last command), the transmitted data word is added to the data structure. for mil-std-1553a mode of operation, all mode codes are defined without data words. for mode codes without data, the data structure contains the message information word and time-tag word only. note: in mil-std-1553a, all mode codes are without data and the t/ r bit is ignored. see section 2.9 for the mil-std-1553a operation. bit mnemonic description number 15-11 wc(4:0) word count bits. these five bits contain word count information extracted from the receive command word bits 15 to 19. 10 n/a not applicable. 9 cha/ b channel a/ b . assertion of this bit indicates that the message was received on the a bus. conversely, if this bit is set to logic zero, the message was received on the b bus. 8 n/a not applicable. 7 me message error. assertion of this bit indicates a message error condition was observed during processing. see bits 0 to 4 for more detail. 6-5 n/a not applicable. 4 ill illegal command received. assertion of this bit indicates the command received was an illegal command. 3 n/a not applicable. 2 ovr overrun error. assertion of this bit indicates the srt received a data word with a transmit command. 1-0 n/a not applicable.
30 s m mmit family 2.3.3.1 mode code receive information (info) word. the following bits describe the mode code receive information word contents . 2.3.3.2 mode code transmit information (info) word. the following bits describe the mode code transmit information word contents. bit mnemonic description number 15-11 mc (4:0) mode code. these five bits contain the mode code information extracted from the receive command word bits 15 to 19. 10 n/a not applicable. 9 cha/ b channel a/ b . assertion of this bit indicates that the message was received on the a bus. conversely, if this bit is set to logic zero, the message was received on the b bus. 8 rtrt remote terminal to remote terminal transfer. assertion of this bit indicates the command processed was a rt-to-rt transfer. 7 me message error. assertion of this bit indicates a message error condition was observed during processing. see bits 0 to 4 for details. 6-5 n/a not applicable. 4 ill illegal command received. assertion of this bit indicates the command received was an illegal command. 3 to time-out error. assertion of this bit indicates the srt did not receive the proper number of data words, i.e., the number of data words received was less than the word count specified in the command word. 2 ovr overrun error. assertion of this bit indicates the srt received a word when none was expected, or the number of data words received was greater than expected. 1 prty parity error. assertion of this bit indicates the srt observed a parity error in the incoming data words. 0 man manchester error. assertion of this bit indicates the srt observed a manchester error in the incoming data words. bit mnemonic description number 15-11 mc (4:0) mode code. these five bits contain the mode code information extracted from the command word bits 15 to 19. 10 n/a not applicable. 9 cha/ b channel a/ b . assertion of this bit indicates that the message was received on the a bus. conversely, if this bit is set to logic zero, the message was received on the b bus. 8 n/a not applicable. 7 me message error. assertion of this bit indicates a message error condition was observed during processing. see bits 0 to 4 for details. 6-5 n/a not applicable. 4 ill illegal command received. assertion of this bit indicates the command received was an illegal command. 3 n/a not applicable. 2 ovr overrun error. assertion of this bit indicates the srt received a data word with a transmit command. 1-0 n/a not applicable.
31 s m mmit family 2.4 mode code and subaddress the s mmm it provides subaddress and mode code decoding that meets mil-std-1553b requirements. in addition, the device has automatic internal illegal command decoding for reserved mil-std-1553b mode codes. table 3 shows the srt?s response to all possible mode code combinations. table 3. mode code descriptions t/r mode code function operation 0 00000-01111 undefined (w/o data) 1. command word stored 2. status word transmitted 0 10000 undefined (with data) 1. command word stored 2. data word stored 3. status word transmitted 0 10001 synchronize (with data) 1. command word stored 2. data word stored 3. time-tag counter loaded with data word value 4. status word transmitted 0 10010 undefined 1. command word stored 2. data word stored 3. status word transmitted 0 10011 undefined 1. command word stored 2. data word stored 3. status word transmitted 0 10100 selected transmitter shutdown 1. command word stored 2. data word stored 3. status word transmitted 0 10101 override selected transmitter shutdown 1. command word stored 2. data word stored 3. status word transmitted 0 10110-11111 reserved 1. command word stored 2. data word stored 3. status word transmitted 1 00000 dynamic bus control 1. command word stored 2. dynamic bus acceptance bit set in outgoing status word if enabled in the control register 3. status word transmitted 1 00001 synchronize 1. command word stored 2. time-tag counter reset to 0000 (hex) 3. status word transmitted 1 00010 transmit status word 1. command word stored 2. last status word transmitted 3. status word cleared after master reset note: srt updates status word if illegalized. 1 00011 initiate self-test 1. command word stored 2. status word transmitted 3. bit initiated 4. tf bit set if bitf bit asserted 1 00100 transmitter shutdown 1. command word stored 2. status word transmitted 3. alternate bus disabled
32 s m mmit family table 3. mode code descriptions (cont.) t/r mode code function operation 1 00101 override transmitter shutdown 1. command word stored 2. status word transmitted 3. alternate bus enabled note: reception of the override transmitter shutdown mode code does not enable a channel not previously enabled in the control register. reset remote terminal mode code clears the transmitter shutdown function. 1 00110 inhibit terminal flag bit 1. command word stored 2. terminal flag bit set to zero and assertion disabled 3. status word transmitted 1 00111 override inhibit terminal flag 1. command word stored 2. terminal flag bit enabled for assertion 3. status word transmitted 1 01000 reset remote terminal 1. command word stored 2. status word transmitted 3. srt reset, see section 2.8 for more information on software reset 1 01001-01111 reserved 1. command word stored 2. status word transmitted 1 10000 transmit vector word 1. command word stored 2. service request bit set to a logic zero in out going status 3. status word transmitted 4. data word transmitted 5. clears the srq bit in the 1553 status word bits register (register 9) 1 10001 reserved 1. command word stored 2. status word transmitted 3. data word transmitted 1 10010 transmit last command 1. command word not stored 2. last status word transmitted 3. last command word transmitted 4. data word stored (transmit last command) 5. transmitted data word is all zero after reset note: the srt stores the transmit last command mode code if illegalized and updates status word. 1 10011 transmit bit word 1. command word stored 2. status word transmitted 3. bit word transmitted from bit word register 4. data word stored (transmit bit word) 1 10100-10101 undefined (with data) 1. command word stored 2. status word transmitted 3. data word transmitted 1 10110-11111 reserved 1. command word stored 2. status word transmitted 3. data word transmitted
33 s m mmit family 2.5 encoder and decoder the srt interfaces directly to a transmitter/receiver via the srt manchester ii encoder/decoder. the srt receives the command word from the mil-std-1553 bus and processes it either by the primary or secondary decoder. each decoder checks for the proper sync pulse and manchester waveform, edge skew, correct number of bits, and parity. if the command is a receive command, the srt processes each incoming data word for correct format, word count, and contiguous data. if a message error is detected, the srt stops processing the remainder of the message (i.e., dmas), suppresses status word transmission, and asserts bit 9 (me bit) of the status word. the srt will track the message until proper word count is finished. the srt automatically compares the transmitted word (encoder word) to the reflected decoder word by way of the continuous loop-back feature. if the encoder word and reflected word do not match, the wrapf bit is asserted in the bit word register and the yf_int will be generated, if enabled. in addition to the loop-back compare test, a timer precludes a transmission greater than 800 m s by the assertion of fail-safe timer ( timerona or timeronb ). this timer is reset upon receipt of another command. remote terminal response time: mil-std-1553a = 7 m s mil-std-1553b = 10 m s data contiguity time-out = 1.0 m s 2.6 rt-rt transfer compare the rt-to-rt terminal address compare logic ensures that the incoming status word?s terminal address matches the terminal address of the transmitting rt specified in the command word. an incorrect match results in setting the message-error bit and suppressing transmission of the status word. (rt-to-rt transfer time-out = 55 to 59 m s). the receiving srt does not check me or ssysf of the transmitting remote terminal. 2.7 terminal address the srt terminal address is programmed via six input pins: rta(4:0) and rtpty. negating mrst latches the srt?s terminal address from pins rta(4:0) and parity bit rtpty. the address and parity cannot change until the next assertion and negation of the mrst input (for lock = 0). the terminal address parity is odd; input pin rtpty is set to a logic state to satisfy this requirement. assertion of operational status register bit 2 (tapf) indicates incorrect terminal address parity. the operational status register bit 2 is valid after the rising edge of mrst . for example: rta(4:0) = 05 (hex) = 00101 (binary) rtpty = 1, sum of 1s = 3 (odd), operational status register bit 2 = 0 rta(4:0) = 04 (hex) = 00100 (binary) rtpty = 0, sum of 1s = 1 (odd), operational status register bit 2 = 0 rta(4:0) = 04 (hex) = 00100 (binary) rtpty = 1, sum of 1s = 2 (even), operational status register bit 2 = 1 note: the srt checks the terminal address and parity after the srt has been started. with broadcast disabled, rta(4:0)=11111 operates as a normal rt address. the bit word register parity fail bit is valid after the srt has been started. the terminal address is also programmed via a write to the operational status register ( lock = 1).the srt loads the terminal address on the completion of the control register write which starts the srt. yf_int occurs if enabled. 2.8 reset the s mmm it provides for several different reset mechanisms. the s mmm it software reset (control register bit 13) is equal to a master reset and takes 5 m s to complete. assertion of this bit results in the immediate reset of the srt and termination of command processing. the host or subsystem is responsible for the re-initialization of the srt for operation. configuration of the device for auto-initialization frees the host or subsystem from this task. a reset remote terminal mode code (mode code 01000, t/ r =1) is equal to a master reset only if autoen is enabled. if autoen is not enabled, the reset remote terminal mode code clears the encoder/decoders, resets the time-tag, enables the channels to the programmed host state, and re-enables the terminal flag for assertion. this reset is performed after the transmission of the 1553 status word. all outputs have asynchronous reset with the following exceptions: dmack , dmar , d(15:0), a(15:0), msg_int , rwr , rcs , and rrd . to reset these signals, apply two clock cycles before the rising edge of mrst .
34 s m mmit family caution: per the mil-std-1553 specification (sections 4.3.3.5.1.7.9 and 30.4.3), a remote terminal must ?complete the reset function within 5 m s following transmission of the status word.? if the autoen function is enabled in the s mmm it, reset may require additional time depending on the application. 2.9 mil-std-1553a operation to maximize flexibility, the s mmm it has been designed to operate in many different systems which use various protocols. specifically, two of the protocols that the s mmm it may be interfaced to are mil-std-1553a and mil-std-1553b. to meet these protocols, the s mmm it may be configured through an external pin or through control register bits (depending on the state of the lock pin). table 4 defines the three ways to program the s mmm it. table 4. mil-std-1553a operation when configured as a remote terminal to meet mil-std- 1553a, the s mmm it will operate as follows: responds with a status word within 7 m s; ignores the t/ r bit for all mode codes; all mode codes are defined without data; all mode codes use mode code transmit control and information words; mode code 00000 is defined as dynamic bus control (dbc); subaddress 00000 defines a mode code; me and tf bits are defined in the 1553 status word; all other status word bits are programmable (i.e., no busy mode, etc.); broadcast of all mode codes, except mode code 00000 (dbc) and mode code 00010 (transmit status word if enabled), is allowed; to illegalize a mode code, the user needs to illegalize both the receive and transmit versions; illegalization of row 1f (hex) is not automatic. a/ b std (pin or bit) xmtsw (bit only) result (protocol selected) 0 x 1553b response, 1553b standard 1 0 1553a response, 1553a standard 1 1 1553a response, auto execute the transmit status word mode code
35 s mmit family 3.0 b u s c o n t r o l l e r a r c h i t e c t u r e the s mmit bus controller (sbc) is an interface device linking a mil-std-1553 serial data bus to a host microprocessor and/or subsystem. the sbc?s architecture is based on a command block structure and internal, programmable registers. designed to run autonomously and reduce host overhead, the sbc?s risc-based core automatically executes data handling, message error checking, memory control, and related protocol functions. this section discusses the following sbc features and functions: multiple message processing message scheduling polling capability executable architecture built-in test interrupt structure memory management 3.1 register descriptions to initialize the s it as a bus controller, the designer must understand the internal registers. the sbc registers offer many programmable functions and allow host access to extensive information. all register bits are active high and reflect a logic zero condition (0000 hex) after master reset (except those reflecting input pins). each register associated with the bus controller mode of operation is individually described below. register number name register address 0 control register 0000 (hex) 1 operational status register 0001 (hex) 2 current command block register 0002 (hex) 3 interrupt mask register 0003 (hex) 4 pending interrupt register 0004 (hex) 5 interrupt log list pointer register 0005 (hex) 6 bit word register 0006 (hex) 7 minor-frame timer 0007 (hex) 8 command block pointer register 0008 (hex) 9 not applicable 0009 (hex) 10 bc command block initialization count register 000a (hex) 11-31 not applicable 000b to 001f (hex) note: reference section 9.1.2 for s mmit xt 8-bit register address numbers.
36 s mmit family 3.1.1 control register (read/write)- register 0 the control register?s function is to configure the s it for operation. to make changes to the sbc and this register, the stex bit (bit 15) must be logic zero. to operate the s it as a bus controller (sbc), use the following bits. bit number mnemonic description 15 stex start execution. assertion of this bit commences operation of the s it. a control register write negating this bit inhibits operation of the s it. after execution begins, a write of logic zero will halt the sbc after completing the current opcode. prior to halting, the sbc determines the next command block pointer address and loads the value into register 8. for an eol command block, register 8 is not updated. 14 sbit start bit. assertion of this bit places the s it into the built-in test routine. the bit test has a fault coverage of 93.4%. once the s it has been started, the host must halt the device in order to place the s it into the built-in test routine (stex = 0) or use the bit opcode. note: if start bit (sbit) and start execution (stex) are both set on one register write, bit has priority. 13 srst software reset. assertion of this bit immediately places the s it into a software reset. like mrst , the software reset (which takes 5 s to execute) clears all internal logic. note: during auto-initialization, do not load this bit with a logic one. srst will only function after readyb is asserted. 12-11 n/a not applicable. 10 etce external timer clock enable. assertion of this bit enables an external clock used with an internal counter for variable minor frame timing. refer to section 3.1.8. note: the user can only change the clock frequency before starting the device (i.e., setting bit 15 of register 0 to a logic one). 9 -- see section 5, enhanced s mmit family operation, for additional information. 8-7 n/a not applicable. 6 bufr buffer mode enable. assertion of this bit enables the buffer mode of operation. refer to section 9.1.5 or 9.2.3 for additional information. 5 n/a not applicable. 4 bcen broadcast enable. assertion of this bit enables the broadcast option for the sbc. negation of this bit enables the remote terminal address 31 as a unique rt address. when enabled, the sbc does not expect a status word response from the remote terminal. 3 n/a not applicable. 2 ppen ping-pong enable. this bit controls the method by which the sbc will retry messages. a logic one allows the sbc to ping-pong between buses during retries. a logic zero dictates that all retries will be performed on the programmed bus as defined in the command block control word. (section 3.2.1 of this document defines the retry bit). 1 inten interrupt log list enable. assertion of this bit enables the interrupt log list. negation of this bit prevents the logging of interrupts as they occur. 0 n/a not applicable.
37 s mmit family 3.1.2 operational status register (read/write) - register 1 this register provides pertinent status information for the sbc and is not reset to 0000 (hex) on mrst . instead, the register reflects the actual stimulus applied to input pins msel(1:0), a/ b std, and lock . assertion of the lock input prevents the modification of the mode selects and the a or b standard bits. in this case, a write to this register?s most significant nine bits is meaning less. if lock is negated, a read of this register reflects the information written into this register?s most significant nine bits. note: to make changes to the sbc and this register, the stex bit (register 0, bit 15) must be logic zero. note: when stex transitions from 0 to 1, ex and teract stay active until command processing is complete. bit number mnemonic description 15-10 n/a not applicable. 9 msel(1) mode select 1. in conjunction with mode select 0, this bit determines the s it mode of operation. 8 msel(0) mode select 0. in conjunction with mode select 1, this bit determines the s it mode of operation. msel(1) msel(0) mode of operation 0 0 bus controller = sbc 0 1 remote terminal = srt 1 0 monitor terminal = smt 1 1 smt/srt 7 a/ b std military standard 1553a or 1553b. this bit determines whether the sbc will operate under mil-std-1553a or 1553b protocol. assertion of this bit forces the sbc to look for all responses in 9 s or generate time-out errors. negation of this bit automatically allows the sbc to operate under the mil-std-1553b protocol. see section 3.6 and section 5.0, enhanced s mmit family operation, for additional information. 6 lock lock pin. this read-only bit reflects the inverted state of the lock input pin and is latched on the rising edge of mrst . 5 autoen autoen pin. this read-only bit defines whether or not the auto enable feature will be used in the design. this bit shows the inverse of the auto enable ( autoen ) input pin. 4 n/a not applicable. 3 ex s it executing. this read-only bit indicates whether the sbc is presently executing or is idle. a logic one indicates that the s it is executing; logic zero indicates the s it is idle. 2 n/a not applicable. 1 ready ready pin. this read-only bit reflects the inverted state of the output pin ready and is cleared on reset. 0 teract teract pin. assertion of this bit indicates that the sbc is presently executing. this read-only bit reflects the inverted state of output pin teract and is cleared on reset.
38 s mmit family 3.1.3 current command register (read-only) - register 2 this register contains the last 1553 command that was transmitted by the sbc. upon the execution of each command block, this register will automatically be updated. this register is updated when transmission of the command word begins. in a rt-rt transf er, the register will reflect the latest command word as it is transmitted. 3.1.4 interrupt mask register (read/write) - register 3 the sbc interrupt architecture allows the host to mask or temporarily disable the service of interrupts. while masked, interrupt activity does not occur. the unmasking of an interrupt after the event occurs does not generate an interrupt for that event. an interrupt is masked if the corresponding bit of this register is set to a logic zero. bit number mnemonic description 15-0 cc(15:0) current command. these bits contain the latest 1553 command that was transmitted by the bus controller. bit number mnemonic description 15 dmaf dma fail interrupt. 14 wrapf wrap fail interrupt. 13 n/a not applicable. 12 bitf bit fail interrupt. 11 merr message error interrupt. 10-6 n/a not applicable. 5 eol end of list interrupt. 4 illcmd illogical command interrupt. 3 illop illogical opcode interrupt. 2 rtf retry fail interrupt. 1 cba command block accessed interrupt. 0 n/a not applicable.
39 s mmit family 3.1.5 pending interrupt register (read-only) - register 4 this register is used to identify which of the interrupts occurred during operation. the assertion of any bit in this register a sserts an output pin, msg_int or yf_int (three clock cycles). writing to the most significant four bits of this register generates a yf_int . note: the user must read or write a s mmit register after reading the pending register to invoke the automatic clear of the pending interrupt register. for example, a subaddress access interrupt results in a pending interrupt register of 0400 16 . a read of the pending interrupt register returns a value of 0400 16 . a subsequent read of the interrupt mask register (i.e., register 3 16 ), followed by a pending interrupt register read returns a value of 0000 16 . the intervening read of the interrupt mask register clears the pending interrupt register at the end of the interrupt mask register read. bit number mnemonic description 15 dmaf dma fail interrupt. once the s it has issued the dmar signal, an internal timer is started. if all dma activity (which includes dmar , dmag , and all dtack ) has not been completed, the interrupt is generated. in the sbc mode, the yf_int interrupt is generated (if not masked) and command processing stops. 14 wrapf wrap fail interrupt. the srt automatically compares the transmitted word (encoder word) to the reflected decoder word by way of the continuous loop-back feature. if the encoder word and reflected word do not match, the wrapf bit asserts and the yf_int interrupt is generated (if not masked). the loop-back path is via the mil-std-1553 bus transceiver. 13 n/a not applicable. 12 bitf bit fail interrupt. assertion of this bit indicates a bit failure. interrogate bit word register bits 11 and 10 to determine the specific failure. in sbc mode, the yf_int interrupt is generated (if not masked) and command processing stops if initiated by opcode. 11 merr message error interrupt. assertion of this bit indicates the occurrence of a message error. the sbc can detect manchester, sync-field, word count, 1553 word parity, bit count, and protocol errors. this bit will be set and an msg_int interrupt generated (if not masked) after message processing is complete. 10-6 n/a not applicable. 5 eol end of list interrupt. assertion of this bit indicates that the sbc is at the end of the command block. msg_int generated (if not masked). 4 illcmd illogical command interrupt. assertion of this bit indicates that an illogical command (i.e., transmit broadcast or improperly formatted rt-rt message) was written into the command block. the sbc checks for rt-rt terminal address field match, rt-rt transmit/receive bit mismatch and correct order, and broadcast transmit commands. if illogical commands occur, the sbc will halt execution. msg_int generated (if not masked). 3 illop illogical opcode interrupt. assertion of this bit indicates an illogical opcode (i.e., any reserved opcode) was used in the command block. the sbc halts operation if this condition occurs. msg_int generated (if not masked). 2 rtf retry fail interrupt. assertion of this bit indicates all programmed retries failed. msg_int generated (if not masked). 1 cba command block accessed interrupt. assertion of this bit indicates a command block was accessed (opcode 1010), if enabled. msg_int generated (if not masked). 0 n/a not applicable.
40 s mmit family 3.1.6 interrupt log list pointer register (read/write) - register 5 the interrupt log list pointer indicates the starting address of the interrupt log list. the interrupt log list is a 32-word rin g- buffer that contains information pertinent to the service of interrupts. the s it architecture requires the location of the interrupt log list on a 32-word boundary. the most significant 11 bits of this register designate the location of the interrupt log list w ithin a 64k memory space. initialize the lower five bits of this register to a logic zero. the s it controls the lower five bits to implement the ring-buffer architecture. the host or subsystem reads this register to determine the location and number of interr upts within the interrupt log list (least significant five bits). 3.1.7 bit word register (read/write) - register 6 this register contains information on the current health of the sbc. the lower eight bits of this register are user-defined. 3.1.8 minor frame timer register (read-only) - register 7 this register is loaded via the minor frame timer (mft) opcode (opcode 1110). for user-defined resolution use tclk. register resets to zero anytime operation halts. bit number mnemonic description 15-0 inta(15:0) interrupt log list pointer bits. these bits indicate the starting location of the interrupt log list. bit number mnemonic description 15 dmaf dma fail. assertion of this bit indicates that all dma activity had not been completed from the time dmar asserts to when the timer decrements to zero (i.e., 16 s). the dma activity includes dmar to dmag , and all wait states. in the event of a dma failure, current processing terminates. 14 wrapf wrap fail. the sbc automatically compares the transmitted word (encoder word) to the reflected decoder word by way of the continuous loop-back feature. if the encoder word and reflected word do not match, the wrapf bit asserts. the loop-back path is via the mil-std-1553 bus transceiver. 13 n/a not applicable. 12 bitf bit fail. assertion of this bit indicates a bit failure. interrogate bit 11 through 8 to determine the specific failure. 11 chaf channel a fail. assertion of this bit indicates a bit test failure in channel a. 10 chbf channel b fail. assertion of this bit indicates a bit test failure in channel b. 9 msbf/udb memory test fail. most significant memory byte failure (s mmit xt). user-defined bits (s mmit & s mmit lx/dx). 8 lsbf/udb memory test fail. least significant memory byte failure (s mmit xt). user-defined bits (s mmit & s mmit lx/dx). 7-0 udb (7:0) user-defined bits. bit number mnemonic description 15-0 mft(15:0) minor frame timer. these bits indicate the value of the timer.
41 s mmit family 3.1.9 command block pointer register (read/write) - register 8 this register contains the location to start the command blocks. after execution begins, this register is automatically updated with the address of the next block. 3.1.10 bc command block initialization count register (read/write)-register 10 this register contains the number of command blocks that will be initialized when using the auto-initialize feature. if 0000 (he x) is written into this register, then no blocks will be set up. because each command block requires eight contiguous memory locati ons, the largest value allowed in this register is 1fff (hex). if a larger value is written into this register, the sbc ignores the t hree most significant bits. bit number mnemonic description 15-0 cba(15:0) command block address. these bits indicate the starting location of the command block. bit number mnemonic description 15-0 cbc(15:0) command block count. these bits indicate the number of command blocks set up during auto-initialization.
42 s mmit family 3.2 sbc architecture as defined in mil-std-1553, the bus controller initiates all communications on the bus. to meet mil-std-1553 bus controller requirements, the s it utilizes a command block architecture that takes advantage of both internal registers and external memory. each command word transmitted over the bus must be associated with a command block. the command block requires eight contiguous memory locations for each message. these eight locations include a control word, two command word locations, a data pointer, two status word locations, a branch address location, and a timer value. the host, or rom for autonomous operation, must initialize each of the locations associated with each command block (the exception is for the two status locations which will be updated as command words are transmitted and corresponding status words are received). figure 8 shows the sbc?s command block architecture while sections 3.2.1 through 3.2.6 describe each location associated with the command block. control word command word 1 command word 2 data pointer status word 1 status word 2 branch address timer value figure 8. command block definition
43 s mmit family 3.2.1 control word the first memory location of each sbc command block contains the control word. each control word contains the opcode, retry number, bus definition, rt-rt instruction, condition codes, and the block access message error. the sbc?s control word is define d below. bit number description 15-12 opcode. these bits define the opcode to be used by the sbc for that particular command block. if the opcode does not perform any 1553 function, all other bits are ignored. each of the available opcodes is defined in section 3.2.1.1. 11-10 retry number. these bits define the number of retries for each individual command block and if a retry opcode is used. if bit 2 of the control register is not enabled, all retries will occur on the programmed bus. however, if bit 2 is enabled, the first retry will always occur on the alternate bus, the second retry will occur on the primary bus, the third retry will occur on the alternate bus, and the fourth retry will occur on the primary bus. bit 11 bit 10 # of retries 0 1 1 1 0 2 1 1 3 0 0 4 9 bus a/ b . this bit defines on which of the two buses the command will be transmitted (i.e., primary bus). (logic 1 = bus a, logic 0 = bus b). 8 rt-rt transfer. this bit defines whether or not the present command block is a rt-rt transfer and if the sbc should transmit the second command word. data associated with a rt-rt is always stored by the sbc (logic 1 = rt-rt). 7-1 condition codes. these bits define the condition code the sbc uses for that particular command block. each of the available condition codes are defined in section 3.2.1.2. 0 block access message error. assertion of this bit indicates a protocol message error occurred in the rt?s response. for this occurrence, the sbc will overwrite this bit prior to storing the control word into memory. noise on the 1553 bus may be one example of such an error. 15 12 11 10 9 8 7 1 0 opcode retry # cha/ b rt-rt condition codes block access me
44 s mmit family 3.2.1.1 opcode definition opcode definition 0000 end of list. this opcode instructs the sbc that the end of the command block has been encountered. command processing stops and the interrupt is generated if the interrupt is enabled. no command processing takes place (i.e., no 1553). 0001 skip. this opcode instructs the sbc to load the message-to-message timer with the value stored in timer value location. the s it will then wait the specified time before proceeding to the next command block. this opcode allows for scheduling of specific time between message execution. no command processing takes place (i.e., no 1553). 0010 go to. this opcode instructs the sbc to ?go to? the command block as specified in the branch address location. no command process takes place (i.e., no 1553). 0011 built-in test. this opcode instructs the sbc to perform an internal built-in test. if the device passes the built-in test, then processing of the next command block will continue. however if the device fails the built-in test, then processing stops and an interrupt is generated, if the interrupt is enabled. no command processing takes place (i.e., no 1553). 0100 execute block; continue. this opcode instructs the sbc to execute the current command block and proceed to the next command block. this opcode allows for continuous operations. 0101 execute block; branch. this opcode instructs the sbc to execute the current command block and unconditionally branch to the location as specified in the branch address location. 0110 execute block; branch on condition. this opcode instructs the sbc to execute the current command block and branch only if the condition is met. if no conditions are met, the opcode appears as an execute and continue. 0111 retry on condition. this opcode instructs the sbc to perform automatic retries, as specified in the control word, if particular conditions occur. if no conditions are met, the opcode appears as an execute and continue. 1000 retry on condition; branch. this opcode instructs the sbc to perform automatic retries, as specified in the control word, if particular conditions occur. if the conditions are met, the sbc retries. once all retries have executed, the sbc branches to the location as specified in the branch address location. if no conditions are met, the opcode appears as an execute and branch. 1001 retry on condition; branch if all retries fail. this opcode instructs the sbc to perform automatic retries, as specified in the control word, if particular conditions occur. if the conditions are met and all the retries fail, the sbc branches to the location as specified in the branch address location. if no conditions are met, the opcode appears as an execute and continue. 1010 interrupt; continue. this opcode instructs the sbc to interrupt and continue processing on the next command block. no command processing takes place (i.e., no 1553). 1011 call. this opcode instructs the sbc to ?go to? the command block as specified in the branch address location without processing this block. the next command block address is saved in an internal register so that the s it may remember one address and return to the next command block. no command processing takes place (i.e., no 1553). 1100 return to call. this opcode instructs the sbc to return to the command block address saved during the call opcode. no command processing takes place (i.e., no 1553). 1101 reserved. the sbc will generate an illegal opcode interrupt (if interrupt enabled) and automatically stop execution if a reserved opcode is used.
45 s mmit family note: for retries with interrupts enabled, all interrupts are logged after message processing is complete. 3.2.1.2 condition codes condition codes have been provided as a means for the sbc to perform certain functions based on the rt?s status word. in a rt- rt transfer, the conditions apply to both of the status words. each bit of the condition codes is defined below. 3.2.2 command words the next two locations of the sbc command block are for 1553 command words. in most 1553 messages, only the first command word needs to be initialized. however, in a rt-rt transfer, the first command word is the receive command and the second command word is the transmit command. 3.2.3 data pointer the fourth location in the sbc command block is the data pointer that points to the first memory location to store or fetch the data words associated with the message for that command block. this data structure allows the sbc to store or fetch the exact specified number of data words, thus saving memory space and providing efficient space allocation. (note: in a rt- rt transfer, the sbc uses the data pointer as the location in memory to store the transmitted data in the transfer.) one common application for the data pointer occurs when the sbc needs to send the same data words to several rts. here, each command block associated with those messages would contain the same data pointer value, and, therefore, fetch and transmit the same data. note that the data pointer is never updated (i.e., the sbc reads and writes the pointer but never changes its value). 1110 load minor frame timer. this opcode instructs the sbc to load the minor frame timer (mft) with the value stored in the eighth location of the current command block. the timer will be loaded after the previous mft has decremented to zero. after the mft timer is loaded with the new value, the sbc will proceed to the next command block. no command processing takes place (i.e., no 1553). 1111 return to branch. this opcode instructs the sbc to return to the command block address saved during a branch opcode. no command processing takes place (i.e., no 1553). bit number description 7 message error. this condition will be met if the sbc detects an error in the rt?s response, or if it detects no response. (the sbc will wait 15 s in 1553b mode and 9 s in 1553a mode before declaring a rt no response.) see section 5.0, enhanced s mmit family operation for additional information. 6 status word response with the message error bit set (bit time 9 in 1553a mode). this condition is met if the sbc detects that the rt?s status word has the message error bit set. 5 status word response with the busy bit set (bit time 16 in 1553a mode). this condition is met if the sbc detects that the rt?s status word has the busy bit set. 4 status word response with the terminal flag bit set (bit time 19 in 1553a mode). this condition is met if the sbc detects that the rt?s status word has the terminal flag bit set. 3 status word response with the subsystem fail bit set (bit time 17 in 1553a mode). this condition is met if the sbc detects that the rt?s status word has the subsystem fail bit set. 2 status word response with the instrumentation bit set (bit time 10 in 1553a mode). this condition is met if the sbc detects that the rt?s status word has the instrumentation bit set. 1 status word response with the service request bit set (bit time 11 in 1553a mode). this condition is met if the sbc detects that the rt?s status word has the service request bit set. opcode definition
46 s mmit family 3.2.4 status words the next two locations in the sbc command block are for status words. as the rt responds to the bc?s command, the corresponding status word will be stored in status word 1. in a rt-rt transfer, the first status word will be the status of the transmitting rt while the second status word will be the status of the receiving rt. 3.2.5 branch address the seventh location in the sbc command block contains the starting location of the branch. this location simply allows the sbc to branch to another location in memory when certain opcodes are used. 3.2.6 timer value the last location in the sbc command block is the timer value. this timer is used for one of two purposes. first, the value may be used to set up minor frame schedules when using the load minor frame timer opcode (1110). the mft counter may be driven by the tclk input. if not driven by the tclk input, the mft counter is clocked at a period of 64 s by an internal clock. the mft counter runs continuously during message processing and must decrement to zero prior to loading the next minor frame time value. second, the value may be used as a message- to-message timer (mmt) when using the skip opcode (0001). the mmt timer is clocked at the 24mhz rate and allows for scheduling of specific time between message execution. 3.3 command block chaining the host determines the first command block by setting the initial start address in the command block pointer register (reg 8). the command blocks will execute in a contiguous fashion as long as no ?go to?, ?branch?, ?call?, or ?return? opcodes are used. with the use of these opcodes, almost any memory configuration is possible. figures 9a, 9b and 10 show how several command blocks may be linked together to form a command frame and how branch opcodes may be used to link minor frames. the minimum bc intermessage gap is 28.0 s.
47 s mmit family figure 9a. minor frame branching minor frame # n service frame conditional branch return error frame retries fail return conditional branch figure 9b. major frame sequencing minor frame #1 minor frame #2 minor frame #n service frame conditional branch return service frame return service frame return conditional branch
48 s mmit family 3.4 memory architecture after reviewing the sbc?s internal registers, it may be advantageous to look at the external memory requirements and how the host sets up memory to make the s it a bus controller. the intent of this section is to show one method for defining the memory configuration. the configuration shows the command blocks, data locations, and the interrupt log list as separate entities within memory. figure 11 shows that the first block of memory is allocated for the command blocks. notice that register 8 initially points to the control word of the first command block. after completing execution of that first command block, register 8 will automatically be updated to show the address associated with the next command block. following the command block locations is the memory required for all the data words. in bc applications, the number of data words for each command block is known. in figure 11 for example, the first command block has allocated several memory locations for expected data. conversely, the second command block has only allocated a few memory locations. since the number of data words associated with each command block is known, memory may be used efficiently. also, shown as a separate memory area is the interrupt log list (refer to section 6.0 for a description of the interrupt log list). notice that register 5 points to the top of the initial log list. after execution of the first sbc command block, register 5 will automatically be updated if interrupt condition exists. figure 10. major frame sequencing minor frame # 1 minor frame # 2 minor frame # n mft mft mft
49 s mmit family 3.5 message processing to process messages, the sbc uses data supplied in the internal registers along with data stored in external memory. the sbc accesses eight words stored in external memory called a command block. the command block is accessed at the beginning and end of command processing. note: in the sbc mode of operation, the s it does not read the command block for each retry situation. the s mmit features two different modes of transferring data to or from ram: buffer and non-buffer. the user selects the buffer or non-buffer transfer mode by setting the bufr bit (bit 6) in the control register. see sections 9.1.5 or 9.2.3 for additional information. the host or subsystem controlling the sbc allocates memory spaces for the minor frame. the top of the command blocks can reside at any address location. defined and entered into memory by the host, the sbc is linked to the command block via the command block pointer register contents. each command block contains a control word, command word 1, command word 2, data pointer, status word 1, status word 2, branch address, and timer value. refer to sections 3.2.1 - 3.2.6 for a complete description of each location. control word information allows the sbc to control the commands transmitted over the 1553 bus. the control word allows the sbc to transmit commands on a specific channel, perform retries, initiate rt-rt transfers, and interrupt on certain conditions. the host or subsystem defines each command word associated with each command block. for normal 1553 commands, only the first command word location will contain valid data. for rt-rt commands, as specified in the control word, the host must define the first command word as a receive and the second command word as a transmit. figure 11. memory architecture for bc mode register command (memory) data storage register interrupt (memory) ctl word cmd words data ptr status words branch ad message timer ctl word cmd words data ptr status words branch ad message timer ctl word cmd words data ptr status words branch ad message timer reg 8 reg 5 int info word cmd block ad int info word cmd block int info word cmd block int info word cmd block int info word cmd block memory
50 s mmit family the sbc reads the command block during minor frame processing (i.e., after assertion of teract ). the sbc arbitrates for the memory bus. after receiving control of the bus, the sbc reads all eight locations. the sbc then surrenders control of the bus (i.e., negates dmack ), and begins the acquisition of data words for either transmission or storage. for a receive command, the data pointer determines where data words are retrieved. the sbc retrieves data words sequentially from the address specified by the data pointer. for a transmit command, the data pointer determines the top memory location. the sbc stores data words sequentially from this top memory location. after transmission or reception, the sbc begins post- processing. command post-processing begins with the arbitration for the memory bus. the sbc performs a dma burst during post-processing. an optional interrupt log entry is performed after a command block update. during the command block update, the sbc modifies the control word as required. 3.6 mil-std-1553a operation to maximize flexibility, the s mmit has been designed to operate in many different systems which use various protocols. specifically, two of the protocols that the s mmit may be interfaced to are mil-std-1553a and mil-std-1553b. to meet these protocols, the s mmit may be configured through an external pin or through control register bits (depending on the state of the lock pin). table 5. mil-std-1553a operation when configured as a mil-std-1553a bus controller, the s it will operate as follows: looks for the rt response within 9 s (see section 5, enhanced s mmit family operation); defines all mode codes without data; defines subaddress 00000 as a mode code. a/ b std (pin) result 0 1553b response, 1553b standard 1 1553a response, 1553a standard
51 s m mmit family 4.0 m o n i t o r t e r m i n a l a r c h i t e c t u r e in many applications, the s m mmit monitor terminal (smt) may be required to be the backup bus controller (bbc). with this in mind, the smt architecture is designed to function like the sbc?s architecture. the smt?s architecture is based on a monitor block structure and internal, programmable registers. designed to run autonomously and reduce host overhead, the smt automatically executes data handling, message error checking, memory control, and related protocol functions. discussed in this section are the following monitor features and functions: command history list executable architecture bit capability interrupt history list monitor all or selected terminals memory management 4.1 register descriptions to initialize the s m mmit as a monitor terminal, the designer must understand the internal registers. a complete description of each register and the associated bits is provided. these registers offer many programmable functions and allow host access to extensive information. all register bits are active high and reflect a logic zero condition (0000 hex) after master reset (except those reflecting input pins). each register associated with the monitor mode of operation is described below. register number name register address 0 control register 0000 (hex) 1 operational status register 0001 (hex) 2 current command block register 0002 (hex) 3 interrupt mask register 0003 (hex) 4 pending interrupt register 0004 (hex) 5 interrupt log list pointer register 0005 (hex) 6 bit word register 0006 (hex) 7 time-tag register 0007 (hex) 8-10 not applicable 0008 to 000a (hex) 11 initial monitor command block pointer register 000b (hex) 12 initial monitor data pointer register 000c (hex) 13 monitor block counter register 000d (hex) 14 monitor filter register 000e (hex) 15 monitor filter register 000f (hex) 16-31 not applicable 0010 to 001f (hex) note: reference section 9.1.2 for s m mmit xt 8-bit register address numbers.
52 s m mmit family 4.1.1 control register (read/write) - register 0 to operate the s m mmit as a monitor terminal, use the following bits. to make changes to the smt and this register, the stex bit (bit 15) must be logic zero. note: the user has 5 m s after teract active to stop execution. bit number mnemonic description 15 stex start execution. assertion of this bit commences operation of the s m mmit. a control register write negating this bit inhibits operation of the s m mmit. after execution has begun, a write of a logic zero will halt the smt after completing the current 1553 message. 14 sbit start bit. assertion of this bit places the s m mmit into the built-in test routine. the bit test has a 93.4% fault coverage. if the s m mmit has been started, the host must halt the device in order to place the s m mmit into the built-in test routine (stex = 0). note: if start bit (sbit) and start execution (stex) are both set on one register write, bit has priority. 13 srst software reset. assertion of this bit immediately places the s m mmit into a software reset. the software reset (which takes 5 m s to execute) clears all internal logic, just as the mrst does. note: during auto- initialization, do not load this bit with a logic one. srst will only function after ready is asserted. 12-11 n/a not applicable. 10 etce external timer clock enable. if this bit is set to logic one, the smt will use the external input clock to drive the time-tag counter. if set to logic zero, the smt will use an internal clock to drive the time tag counter. refer to section 4.1.8 for additional information. note: the user can only change the clock frequency before starting the device (i.e., setting bit 15 of register 0 to a logic one). 9 -- see section 5, enhanced s m mmit family operation. 8-7 n/a not applicable. 6 bufr buffer mode enable. assertion of this bit enables the buffer mode of operation. for more detailed information on this feature refer to section 9.1.5 and 9.2.3. 5 smtc monitor control. this bit determines whether the smt will monitor all rts or selected rts. if this bit is set to logic zero, the smt will monitor all rts. if this bit is set to logic one, the smt will monitor only the rts as specified in the monitor filter registers (registers 14 and 15). 4 bcen broadcast enable. this bit, if set to logic one, allows rt address 31 to be used as a broadcast message. if set to logic zero, then address 31 is a normal address. 3-2 n/a not applicable. 1 inten interrupt log list enable. assertion of this bit enables the interrupt log list. negation of this bit prevents the logging of interrupts as they occur. 0 n/a not applicable.
53 s m mmit family 4.1.2 operational status register (read/write) - register 1 this register reflects pertinent status information for the smt and is not reset to 0000 (hex) on mrst . instead, the register reflects the actual stimulus applied to input pins msel(1:0), a/ b std, and lock . assertion of the lock input prevents the modification of the remote terminal address, mode selects, and the a or b standard bits. in this case, a write to this register?s most signif icant nine bits is meaningless. if lock is negated, a read of this register reflects the information written into this register?s most significant nine bits. note: to make changes to the smt and this register, the stex bit (register 0, bit 15) must be logic zero. bit number mnemonic description 15-10 n/a not applicable. 9 msel(1) mode select 1. in conjunction with mode select 0, this bit determines the s m mmit mode of operation. 8 msel(0) mode select 0. in conjunction with mode select 1, this bit determines the s m mmit mode of operation. msel(1) msel(0) mode of operation 0 0 bus controller = sbc 0 1 remote terminal = srt 1 0 monitor terminal = smt 1 1 smt/srt 7 a/ b std military standard 1553a or 1553b standard. this bit determines whether the smt will look for the rt?s response in 9 m s (mil-std- 1553a) or in 15 m s (mil-std-1553b). assertion of this bit forces the smt to declare a time-out error condition if the rt has not responded in 9 m s. negation of this bit allows the smt to declare a time-out error condition if the rt has not responded in 15 m s. see section 4.7 and section 5.0, enhanced s m mmit family operation, for additional information. 6 lock lock pin. this read-only bit reflects the inverted state of the lock input pin. the lock pin is latched on the rising edge of mrst . if modes of operation must change, the user must perform a mrst. 5 autoen autoen pin. this read-only bit defines whether or not the auto enable feature will be used in the design. this bit shows the inverse of the auto enable ( autoen ) input pin. 4 n/a not applicable. 3 ex s m mmit executing. this read-only bit indicates whether the smt is presently executing or whether it is idle. a logic one indicates that the s m mmit is executing, logic zero idle. 2 n/a not applicable. 1 ready ready pin. this read-only bit reflects the inverted state of the output pin ready and is cleared on reset. 0 teract terminal active pin. assertion of this bit indicates that the smt is presently processing a message. this read-only bit reflects the inverted state of output pin teract and is cleared on reset.
54 s m mmit family 4.1.3 current command register (read-only) - register 2 this register contains the last valid command that was transmitted over the 1553 bus. in a rt-rt transfer, this register will up date as each of the two commands are received by the smt. 4.1.4 interrupt mask register (read/write) - register 3 the smt interrupt architecture allows the host or subsystem to mask or temporarily disable the service of interrupts. while mask ed, interrupt activity does not occur. the unmasking of an interrupt after the event occurs does not generate an interrupt for that event. an interrupt is masked if the corresponding bit of this register is set to logic zero. bit number mnemonic description 15-0 cc(15:0) current command. these bits contain the latest 1553 word that was received by the smt. bit number mnemonic description 15 dmaf dma fail interrupt. 14-13 n/a not applicable. 12 bitf bit fail interrupt. 11 merr message error interrupt. 10-1 n/a not applicable. 0 mbc monitor block counter interrupt.
55 s m mmit family 4.1.5 pending interrupt register (read-only) - register 4 the pending interrupt register contains information that identifies events that generate interrupts. the assertion of any bit in this register asserts an output pin, msg_int or yf_int (three clock cycles). writing to the most significant four bits of this register generates a yf_int . note: the user must read or write a s m mmit register after reading the pending register to invoke the automatic clear of the pending interrupt register. for example, a subaddress access interrupt results in a pending interrupt register of 0400 16 . a read of the pending interrupt register returns a value of 0400 16 . a subsequent read of the interrupt mask register (i.e., register 3 16 ), followed by a pending interrupt register read returns a value of 0000 16 . the intervening read of the interrupt mask register clears of the pending interrupt register at the end of the interrupt mask register read. 4.1.6 interrupt log list pointer register (read/write) - register 5 this register indicates the starting address of the interrupt log list. the interrupt log list is a 32-word ring-buffer that con tains information pertinent to the service of interrupts. the s m mmit architecture requires the location of the interrupt log list on a 32- word boundary. the most significant 11 bits of this register designate the location of the interrupt log list within a 32k memor y space. initialize the lower five bits of this register to a logic zero. the s m mmit controls the lower five bits to implement the ring- buffer architecture. the host or subsystem reads this register to determine the location and number of interrupts within the int errupt log list (least significant five bits). bit number mnemonic description 15 dmaf dma fail interrupt. once the s m mmit has issued the dmar signal, an internal timer is started. if all dma activity has not been completed, the interrupt is generated (if not masked). in the smt mode, the yf_int interrupt is generated, current command processing will end, and the smt will remain on-line. 14-13 n/a not applicable. 12 bitf bit fail interrupt. assertion of this bit indicates a bit failure. interrogate the bit word register to determine the specific failure. yf_int interrupt generated (if not masked), operation continues. 11 merr message error interrupt. this bit is set if a message error occurs. the smt can detect manchester, sync-field, word count, 1553 word parity, bit count, and protocol errors. this bit will be set and interrupt generated after message processing is complete. msg_int interrupt generated (if not masked). 10-1 n/a not applicable. 0 mbc monitor block counter interrupt. this bit is set if the smt?s monitor block counter reaches zero (transition from 1 to 0). it should be noted that the smt does not discriminate between error-free messages and those messages with errors. msg_int interrupt generated (if not masked). bit number mnemonic description 15-0 inta(15:0) interrupt log list pointer bits. these bits indicate the starting location of the interrupt log list.
56 s m mmit family 4.1.7 bit word register (read/write)- register 6 this register contains information on the current health of the smt. the lower eight bits of this register are user-defined. 4.1.8 time-tag register (read/write) - register 7 this register reflects the state of a 16-bit free running ring counter. this counter will remain a free running counter as long as the device is not in mrst or in a software reset state. the resolution of this counter is user-defined via input tclk or fixed at a period of 64 m s. the time-tag counter begins operation on the rising edge to mrst . 4.1.9 initial monitor block pointer register (read/write) - register 11 this register contains the starting location of the monitor blocks. note: it is recommended that this register not be changed while the smt is active (i.e., register 1, bit 3 = 1). bit number mnemonic description 15 dmaf dma fail. this bit is set if all dma activity has not been completed between the time dmar asserts and when the timer decrements to zero. the dma activity includes dmar to dmag and all wait states. in the event of a dma failure, current message processing terminates; monitor terminal waits for next 1553 message. 14-13 n/a not applicable. 12 bitf bit fail. assertion of this bit indicates a bit failure. interrogate bits 11 through 8 to determine the specific failure. 11 chaf channel a fail. assertion of this bit indicates a bit test failure in channel a. 10 chbf channel b fail. assertion of this bit indicates a bit test failure in channel b. 9 msbf memory test fail. most significant memory byte failure (s m mmit xt). user-defined bits (s m mmit & s m mmit lx/dx). 8 lsbf memory test fail. least significant memory byte failure (s m mmit xt). user-defined bits (s m mmit & s m mmit lx/dx). 7-0 udb(7:0) user-defined bits. bit number mnemonic description 15-0 tt(15:0) time-tag counter bits. these bits indicate the state of the 16-bit internal counter. bit number mnemonic description 15-0 mba(15:0) initial monitor block address. these bits indicate the starting location of the monitor block.
57 s m mmit family 4.1.10 initial monitor data pointer register (read/write) - register 12 this register contains the starting location of the monitor data. note: it is recommended that this register not be changed while the smt is active (i.e., register 1, bit 3 = 1). 4.1.11 monitor block counter register (read/write) - register 13 this register contains the number of the monitor block the user wishes to log. after execution begins, this register automatical ly decrements as commands are logged. when this register is decremented from one to zero, an interrupt will be generated, if enable d. the smt will start over at the initial pointers as identified in registers 11 and 12. note: it is recommended that this register not be changed while the smt is active (i.e., register 1, bit 3 = 1). 4.1.12 monitor filter register (read/write) - register 14 this register determines which rts (rt 31 through rt 16) the smt will monitor. reset value is 0000 (hex). a logical "1" indicate s the monitor captures all data to and from the remote terminal. 4.1.13 monitor filter register (read/write) - register 15 this register determines which rts (rt 15 through rt 0) the smt will monitor. reset value is 0000 (hex). a logical "1" indicates the monitor captures all data to and from the remote terminal. bit number mnemonic description 15-0 mda(15:0) initial monitor data address. these bits indicate the starting location of the monitor data. bit number mnemonic description 15-0 mbc(15:0) monitor block count. these bits indicate the number of monitor blocks to log. bit number mnemonic description 15-0 mf(31:16) monitor filter. these bits determine which rt to monitor. bit number mnemonic description 15-0 mf(15:0) monitor filter. these bits determine which rt to monitor.
58 s m mmit family 4.2 smt architecture to meet the mil-std-1553 monitor requirements, the smt utilizes a monitor block architecture that takes advantage of both internal registers and external memory. the monitor block, which is located in external contiguous memory, requires eight locations for each message. these eight locations include a message information word, two command word locations, a data pointer, two status word locations, a time-tag location, and an unused location. the host, or rom for autonomous operation, must initialize the starting locations of the monitor block, the data pointer, block counter, and the interrupt log pointer. from then on, the smt will build a monitor block for each message it receives over the 1553 bus. figure 11 shows a diagram of the monitor block followed by a description of each location associated with the monitor block. the first memory location of each monitor block contains the message information word. each message information word contains the opcode, retry number, bus definition, rt-rt messages, and the message information. figure 12. monitor block diagram 4.2.1 message information word message information word command word 1 command word 2 data pointer status word 1 status word 2 time-tag unused bit number description 15-12 default. with the monitor block architecture resembling the sbc command block architecture, these bits default to a ?0100? state (which is the execute and continue opcode) in case the monitor must switch to the bc mode of operation. 11-10 default. with the monitor block architecture resembling the sbc, these bits default to a ?00? state. if the monitor must switch to the bc, the retries will be set at four per message. 9 channel a/ b . this bit defines on which of the two buses the command was received. (logic 1 = bus a, logic 0 = bus b). 8 rt-rt transfer. this bit defines whether or not the message associated with this monitor block was a rt-rt transfer and whether the smt saved the second command word. this bit will be set only if the smt is instructed to monitor the receive rt. 7-0 message information. these bits define the conditions of the message received by the smt for that particular monitor block. each of the message information bits is defined in the following section. 15 12 11 10 9 8 7 0 0 1 0 0 0 0 cha/ b rt-rt message information
59 s m mmit family 4.2.1.1 message information bits message information bits are provided as a means to supply more data on the message. in a rt-rt transfer, the information applie s to the complete message. each message information bit is defined below. 4.2.2 command words the next two locations in the smt monitor block are for command words. in non-rt-rt 1553 messages, only the first command word will be stored. however, in a rt-rt transfer, the first command word is the receive command and the second command word is the transmit command. 4.2.3 data pointer the fourth location in the smt monitor block is the data pointer. this pointer points to the first memory location to store the data words associated with the message for this block. note that the data associated with each individual message will be stored contiguously. this data structure allows the smt to store the specified number of data words. (note: in a rt-rt transfer, the smt uses the data pointer as the location in memory to store the transmitting data in the transfer.) 4.2.4 status words the next two locations in the smt monitor block are for status words. as the rt responds to the bc?s command, the corresponding status word will be stored in status word 1. however, in a rt-rt transfer, the first status word will be the status of the transmitting rt while the second status word will be the status of the receiving rt. 4.2.5 time-tag the seventh location in the smt monitor block is the time-tag associated with the message. the time-tag is stored into this location at the end of message processing (i.e., captured after the command is validated). 4.2.6 unused the last location in the smt monitor block is unused. bit number description 7 message error. this bit will be set if the monitor detects an error in either the command word, data words, or the rt?s status. 6 mode code without data. this bit will be set if the monitor detects that the command being processed is a mode code without data words. 5 broadcast. this bit will be set if the monitor detects that the command being processed is a broadcast message. 4 reserved. 3 time-out error. this bit will be set if the srt did not receive the proper number of data words, e.g., the number of data words received was less than the word count specified in the command word. 2 overrun error. this bit will be set if the srt received a word when none were expected or the number of data words received was greater than expected. 1 parity error. this bit will be set if a parity error has occurred on the data words or the rt?s status word. 0 manchester error. this bit will be set if a manchester error has occurred on either the data words or the rt?s status word.
60 s m mmit family 4.3 monitor block chaining the host determines the first monitor block by setting the start address in the initial monitor block pointer register (register 11). figure 13 shows the smt monitor blocks as the blocks execute in a contiguous fashion (monitor block count register 13 = 5). 4.4 memory architecture figure 14 shows the monitor blocks, data locations, and the interrupt log list as separate entities within memory. the configuration shows that the first block of memory is allocated for the monitor blocks. notice that register 11 points to the initial monitor block location, register 12 points to the initial data location, register 5 points to the interrupt log, and register 13 contains the monitor block count. after execution begins, the smt will build command blocks and store data words until the count reaches zero. when the count reaches zero, the smt will simply wrap back to the initial values and start again. figure 14. memory architecture for monitor mode initial monitor command block pointer register monitor (memory) data storage initial monitor data pointer register interrupt (memory) msg info word cmd words data ptr status words time-tag unused reg 11 memory int info word monitor block reg 12 interrupt log list pointer register reg 5 msg info word cmd words data ptr status words time-tag unused msg info word cmd words data ptr status words time-tag unused monitor block #4 monitor block #1 monitor block #2 monitor block #3 monitor block #6 monitor block #5 figure 13. monitor block structuring monitor block count = 5 monitor block count = 4 monitor block count = 3 monitor block count = 2 monitor block count = 1 monitor block count = 0
61 s m mmit family 4.5 message processing to process messages, the smt uses data supplied in the internal registers along with external memory. the smt uses eight external memory locations for each message called a monitor block. the monitor block is updated at the end of command processing. the following paragraphs discuss the monitor block in detail. the s m mmit features two different modes of transferring data to ram: buffer and non-buffer. the user selects the buffer or non-buffer transfer mode by setting the bufr bit (bit 6) in the control register. see sections 9.1.5 or 9.2.3 for additional information. the host or subsystem controlling the smt allocates memory spaces for each monitor block. the top of the monitor blocks can reside at any address location. initialized by the host, the smt is linked to the monitor block via the initial monitor block pointer register and the monitor block counter register contents. each monitor block contains a message information word, command word 1, command word 2, data pointer, status word 1, status word 2, and time-tag. refer to sections 4.2.1 - 4.2.6 for a full description of each location. the message information word allows the smt to tell the host or subsystem on which bus the command was received, whether the message was a rt-rt transfer, and conditions associated with the message. the smt also stores each command word associated with the message into the appropriate location. for normal 1553 commands, only the first command word location will contain data. for rt-rt commands, the second command word location will contain data, and bit 8 in the message information word will be set. for each command, the data pointer determines where to store data words. the smt stores data sequentially from the top memory location. the smt also stores each status word associated with the message into the appropriate location. for normal 1553 commands, only the first status word location will contain data. for rt-rt commands, the second status word location will contain data.the smt begins monitoring after control register bit 15=1 (i.e., assertion of stex). after reception, the smt begins post-processing. the smt performs a dma burst during post-processing. an optional interrupt log entry is performed after a monitor block is entered. monitor time-out: mil-std-1553a = 9 m s mil-std-1553b = 15 m s see section 5, enhanced s m mmit family operation for additional information. 4.5.1 error condition message processing when the monitor detects an error condition in either the command word, data words, or the rt?s status, the monitor block will not store the data. the monitor block counter increments. the initial message data pointer remains constant. the monitor block pointer increments. message information bits of the monitor block are changed to reflect the error. an interrupt is given indicating a message has occurred. see section 4.2.1.1 for additional information. 4.6 remote terminal/monitor terminal operation for applications that require simultaneous remote terminal and monitor terminal operations, the s m mmit should be configured as both a remote terminal (srt) and monitor terminal (smt). this feature allows the srt to communicate on the bus for one specific address and the smt to monitor the bus for other specific addresses. configuration as both smt and srt precludes the s m mmit from monitoring its own remote terminal address. when the s m mmit is configured as both srt and smt, the srt has priority over the smt. for example, commands to the srt will always take priority over monitoring functions for the smt. the examples below describe what happens if the srt is defined as terminal address 1 and the smt is to monitor terminal address 12. example 1: in this example, the smt will decode the first command on bus a, realize the message is for terminal address 12, and start monitoring the message. however, as soon as the srt realizes the second command on bus b is to terminal address 1, the srt will take priority and begin srt message processing. example 2: bus a bus b cmd/ta =12 cmd/ta =1 bus a bus b cmd/ta =1 cmd/ta =12
62 s m mmit family in example 2, the srt will decode the first command on bus a, realize the message is for terminal address 1, and start message processing. as the message on bus b is received, the s m mmit will realize it is to terminal address 12, but since the srt has priority the smt will not switch to the monitor mode. the above examples also apply to a rt-rt message. for example, if the first command in a rt-rt transfer matches the terminal address of the srt, the entire message will be processed by the srt (message 1). however, if the first command in a rt-rt transfer matches the terminal address of the smt and the second command matches the terminal address of the srt, the srt will take priority and process the message (message 2). below is a rt-rt message example. 4.7 mil-std-1553a operation to maximize flexibility, the s m mmit has been designed to operate in many different systems which use various protocols. specifically, two of the protocols that the s m mmit may be interfaced to are mil-std-1553a and mil-std-1553b. to meet these protocols, the s m mmit may be configured through an external pin or through control register bits (depending on the state of the lock pin). table 6. mil-std-1553a operation when configured as a mil-std-1553a monitor, the s m mmit will operate as follows: looks for the rt response within 9 m s (see section 5, enhanced s m mmit family operation); defines all mode codes without data; defines subaddress 00000 as a mode code. message 1 message 2 cmd/ta =1 cmd/ta =12 cmd/ta =12 cmd/ta =1 a/ b std (pin) result 0 1553b response, 1553b standard 1 1553a response, 1553a standard
51 s m mmit family 4.0 m o n i t o r t e r m i n a l a r c h i t e c t u r e in many applications, the s m mmit monitor terminal (smt) may be required to be the backup bus controller (bbc). with this in mind, the smt architecture is designed to function like the sbc?s architecture. the smt?s architecture is based on a monitor block structure and internal, programmable registers. designed to run autonomously and reduce host overhead, the smt automatically executes data handling, message error checking, memory control, and related protocol functions. discussed in this section are the following monitor features and functions: command history list executable architecture bit capability interrupt history list monitor all or selected terminals memory management 4.1 register descriptions to initialize the s m mmit as a monitor terminal, the designer must understand the internal registers. a complete description of each register and the associated bits is provided. these registers offer many programmable functions and allow host access to extensive information. all register bits are active high and reflect a logic zero condition (0000 hex) after master reset (except those reflecting input pins). each register associated with the monitor mode of operation is described below. register number name register address 0 control register 0000 (hex) 1 operational status register 0001 (hex) 2 current command block register 0002 (hex) 3 interrupt mask register 0003 (hex) 4 pending interrupt register 0004 (hex) 5 interrupt log list pointer register 0005 (hex) 6 bit word register 0006 (hex) 7 time-tag register 0007 (hex) 8-10 not applicable 0008 to 000a (hex) 11 initial monitor command block pointer register 000b (hex) 12 initial monitor data pointer register 000c (hex) 13 monitor block counter register 000d (hex) 14 monitor filter register 000e (hex) 15 monitor filter register 000f (hex) 16-31 not applicable 0010 to 001f (hex) note: reference section 9.1.2 for s m mmit xt 8-bit register address numbers.
52 s m mmit family 4.1.1 control register (read/write) - register 0 to operate the s m mmit as a monitor terminal, use the following bits. to make changes to the smt and this register, the stex bit (bit 15) must be logic zero. note: the user has 5 m s after teract active to stop execution. bit number mnemonic description 15 stex start execution. assertion of this bit commences operation of the s m mmit. a control register write negating this bit inhibits operation of the s m mmit. after execution has begun, a write of a logic zero will halt the smt after completing the current 1553 message. 14 sbit start bit. assertion of this bit places the s m mmit into the built-in test routine. the bit test has a 93.4% fault coverage. if the s m mmit has been started, the host must halt the device in order to place the s m mmit into the built-in test routine (stex = 0). note: if start bit (sbit) and start execution (stex) are both set on one register write, bit has priority. 13 srst software reset. assertion of this bit immediately places the s m mmit into a software reset. the software reset (which takes 5 m s to execute) clears all internal logic, just as the mrst does. note: during auto- initialization, do not load this bit with a logic one. srst will only function after ready is asserted. 12-11 n/a not applicable. 10 etce external timer clock enable. if this bit is set to logic one, the smt will use the external input clock to drive the time-tag counter. if set to logic zero, the smt will use an internal clock to drive the time tag counter. refer to section 4.1.8 for additional information. note: the user can only change the clock frequency before starting the device (i.e., setting bit 15 of register 0 to a logic one). 9 -- see section 5, enhanced s m mmit family operation. 8-7 n/a not applicable. 6 bufr buffer mode enable. assertion of this bit enables the buffer mode of operation. for more detailed information on this feature refer to section 9.1.5 and 9.2.3. 5 smtc monitor control. this bit determines whether the smt will monitor all rts or selected rts. if this bit is set to logic zero, the smt will monitor all rts. if this bit is set to logic one, the smt will monitor only the rts as specified in the monitor filter registers (registers 14 and 15). 4 bcen broadcast enable. this bit, if set to logic one, allows rt address 31 to be used as a broadcast message. if set to logic zero, then address 31 is a normal address. 3-2 n/a not applicable. 1 inten interrupt log list enable. assertion of this bit enables the interrupt log list. negation of this bit prevents the logging of interrupts as they occur. 0 n/a not applicable.
53 s m mmit family 4.1.2 operational status register (read/write) - register 1 this register reflects pertinent status information for the smt and is not reset to 0000 (hex) on mrst . instead, the register reflects the actual stimulus applied to input pins msel(1:0), a/ b std, and lock . assertion of the lock input prevents the modification of the remote terminal address, mode selects, and the a or b standard bits. in this case, a write to this register?s most signif icant nine bits is meaningless. if lock is negated, a read of this register reflects the information written into this register?s most significant nine bits. note: to make changes to the smt and this register, the stex bit (register 0, bit 15) must be logic zero. bit number mnemonic description 15-10 n/a not applicable. 9 msel(1) mode select 1. in conjunction with mode select 0, this bit determines the s m mmit mode of operation. 8 msel(0) mode select 0. in conjunction with mode select 1, this bit determines the s m mmit mode of operation. msel(1) msel(0) mode of operation 0 0 bus controller = sbc 0 1 remote terminal = srt 1 0 monitor terminal = smt 1 1 smt/srt 7 a/ b std military standard 1553a or 1553b standard. this bit determines whether the smt will look for the rt?s response in 9 m s (mil-std- 1553a) or in 15 m s (mil-std-1553b). assertion of this bit forces the smt to declare a time-out error condition if the rt has not responded in 9 m s. negation of this bit allows the smt to declare a time-out error condition if the rt has not responded in 15 m s. see section 4.7 and section 5.0, enhanced s m mmit family operation, for additional information. 6 lock lock pin. this read-only bit reflects the inverted state of the lock input pin. the lock pin is latched on the rising edge of mrst . if modes of operation must change, the user must perform a mrst. 5 autoen autoen pin. this read-only bit defines whether or not the auto enable feature will be used in the design. this bit shows the inverse of the auto enable ( autoen ) input pin. 4 n/a not applicable. 3 ex s m mmit executing. this read-only bit indicates whether the smt is presently executing or whether it is idle. a logic one indicates that the s m mmit is executing, logic zero idle. 2 n/a not applicable. 1 ready ready pin. this read-only bit reflects the inverted state of the output pin ready and is cleared on reset. 0 teract terminal active pin. assertion of this bit indicates that the smt is presently processing a message. this read-only bit reflects the inverted state of output pin teract and is cleared on reset.
54 s m mmit family 4.1.3 current command register (read-only) - register 2 this register contains the last valid command that was transmitted over the 1553 bus. in a rt-rt transfer, this register will up date as each of the two commands are received by the smt. 4.1.4 interrupt mask register (read/write) - register 3 the smt interrupt architecture allows the host or subsystem to mask or temporarily disable the service of interrupts. while mask ed, interrupt activity does not occur. the unmasking of an interrupt after the event occurs does not generate an interrupt for that event. an interrupt is masked if the corresponding bit of this register is set to logic zero. bit number mnemonic description 15-0 cc(15:0) current command. these bits contain the latest 1553 word that was received by the smt. bit number mnemonic description 15 dmaf dma fail interrupt. 14-13 n/a not applicable. 12 bitf bit fail interrupt. 11 merr message error interrupt. 10-1 n/a not applicable. 0 mbc monitor block counter interrupt.
55 s m mmit family 4.1.5 pending interrupt register (read-only) - register 4 the pending interrupt register contains information that identifies events that generate interrupts. the assertion of any bit in this register asserts an output pin, msg_int or yf_int (three clock cycles). writing to the most significant four bits of this register generates a yf_int . note: the user must read or write a s m mmit register after reading the pending register to invoke the automatic clear of the pending interrupt register. for example, a subaddress access interrupt results in a pending interrupt register of 0400 16 . a read of the pending interrupt register returns a value of 0400 16 . a subsequent read of the interrupt mask register (i.e., register 3 16 ), followed by a pending interrupt register read returns a value of 0000 16 . the intervening read of the interrupt mask register clears of the pending interrupt register at the end of the interrupt mask register read. 4.1.6 interrupt log list pointer register (read/write) - register 5 this register indicates the starting address of the interrupt log list. the interrupt log list is a 32-word ring-buffer that con tains information pertinent to the service of interrupts. the s m mmit architecture requires the location of the interrupt log list on a 32- word boundary. the most significant 11 bits of this register designate the location of the interrupt log list within a 32k memor y space. initialize the lower five bits of this register to a logic zero. the s m mmit controls the lower five bits to implement the ring- buffer architecture. the host or subsystem reads this register to determine the location and number of interrupts within the int errupt log list (least significant five bits). bit number mnemonic description 15 dmaf dma fail interrupt. once the s m mmit has issued the dmar signal, an internal timer is started. if all dma activity has not been completed, the interrupt is generated (if not masked). in the smt mode, the yf_int interrupt is generated, current command processing will end, and the smt will remain on-line. 14-13 n/a not applicable. 12 bitf bit fail interrupt. assertion of this bit indicates a bit failure. interrogate the bit word register to determine the specific failure. yf_int interrupt generated (if not masked), operation continues. 11 merr message error interrupt. this bit is set if a message error occurs. the smt can detect manchester, sync-field, word count, 1553 word parity, bit count, and protocol errors. this bit will be set and interrupt generated after message processing is complete. msg_int interrupt generated (if not masked). 10-1 n/a not applicable. 0 mbc monitor block counter interrupt. this bit is set if the smt?s monitor block counter reaches zero (transition from 1 to 0). it should be noted that the smt does not discriminate between error-free messages and those messages with errors. msg_int interrupt generated (if not masked). bit number mnemonic description 15-0 inta(15:0) interrupt log list pointer bits. these bits indicate the starting location of the interrupt log list.
56 s m mmit family 4.1.7 bit word register (read/write)- register 6 this register contains information on the current health of the smt. the lower eight bits of this register are user-defined. 4.1.8 time-tag register (read/write) - register 7 this register reflects the state of a 16-bit free running ring counter. this counter will remain a free running counter as long as the device is not in mrst or in a software reset state. the resolution of this counter is user-defined via input tclk or fixed at a period of 64 m s. the time-tag counter begins operation on the rising edge to mrst . 4.1.9 initial monitor block pointer register (read/write) - register 11 this register contains the starting location of the monitor blocks. note: it is recommended that this register not be changed while the smt is active (i.e., register 1, bit 3 = 1). bit number mnemonic description 15 dmaf dma fail. this bit is set if all dma activity has not been completed between the time dmar asserts and when the timer decrements to zero. the dma activity includes dmar to dmag and all wait states. in the event of a dma failure, current message processing terminates; monitor terminal waits for next 1553 message. 14-13 n/a not applicable. 12 bitf bit fail. assertion of this bit indicates a bit failure. interrogate bits 11 through 8 to determine the specific failure. 11 chaf channel a fail. assertion of this bit indicates a bit test failure in channel a. 10 chbf channel b fail. assertion of this bit indicates a bit test failure in channel b. 9 msbf memory test fail. most significant memory byte failure (s m mmit xt). user-defined bits (s m mmit & s m mmit lx/dx). 8 lsbf memory test fail. least significant memory byte failure (s m mmit xt). user-defined bits (s m mmit & s m mmit lx/dx). 7-0 udb(7:0) user-defined bits. bit number mnemonic description 15-0 tt(15:0) time-tag counter bits. these bits indicate the state of the 16-bit internal counter. bit number mnemonic description 15-0 mba(15:0) initial monitor block address. these bits indicate the starting location of the monitor block.
57 s m mmit family 4.1.10 initial monitor data pointer register (read/write) - register 12 this register contains the starting location of the monitor data. note: it is recommended that this register not be changed while the smt is active (i.e., register 1, bit 3 = 1). 4.1.11 monitor block counter register (read/write) - register 13 this register contains the number of the monitor block the user wishes to log. after execution begins, this register automatical ly decrements as commands are logged. when this register is decremented from one to zero, an interrupt will be generated, if enable d. the smt will start over at the initial pointers as identified in registers 11 and 12. note: it is recommended that this register not be changed while the smt is active (i.e., register 1, bit 3 = 1). 4.1.12 monitor filter register (read/write) - register 14 this register determines which rts (rt 31 through rt 16) the smt will monitor. reset value is 0000 (hex). a logical "1" indicate s the monitor captures all data to and from the remote terminal. 4.1.13 monitor filter register (read/write) - register 15 this register determines which rts (rt 15 through rt 0) the smt will monitor. reset value is 0000 (hex). a logical "1" indicates the monitor captures all data to and from the remote terminal. bit number mnemonic description 15-0 mda(15:0) initial monitor data address. these bits indicate the starting location of the monitor data. bit number mnemonic description 15-0 mbc(15:0) monitor block count. these bits indicate the number of monitor blocks to log. bit number mnemonic description 15-0 mf(31:16) monitor filter. these bits determine which rt to monitor. bit number mnemonic description 15-0 mf(15:0) monitor filter. these bits determine which rt to monitor.
58 s m mmit family 4.2 smt architecture to meet the mil-std-1553 monitor requirements, the smt utilizes a monitor block architecture that takes advantage of both internal registers and external memory. the monitor block, which is located in external contiguous memory, requires eight locations for each message. these eight locations include a message information word, two command word locations, a data pointer, two status word locations, a time-tag location, and an unused location. the host, or rom for autonomous operation, must initialize the starting locations of the monitor block, the data pointer, block counter, and the interrupt log pointer. from then on, the smt will build a monitor block for each message it receives over the 1553 bus. figure 11 shows a diagram of the monitor block followed by a description of each location associated with the monitor block. the first memory location of each monitor block contains the message information word. each message information word contains the opcode, retry number, bus definition, rt-rt messages, and the message information. figure 12. monitor block diagram 4.2.1 message information word message information word command word 1 command word 2 data pointer status word 1 status word 2 time-tag unused bit number description 15-12 default. with the monitor block architecture resembling the sbc command block architecture, these bits default to a ?0100? state (which is the execute and continue opcode) in case the monitor must switch to the bc mode of operation. 11-10 default. with the monitor block architecture resembling the sbc, these bits default to a ?00? state. if the monitor must switch to the bc, the retries will be set at four per message. 9 channel a/ b . this bit defines on which of the two buses the command was received. (logic 1 = bus a, logic 0 = bus b). 8 rt-rt transfer. this bit defines whether or not the message associated with this monitor block was a rt-rt transfer and whether the smt saved the second command word. this bit will be set only if the smt is instructed to monitor the receive rt. 7-0 message information. these bits define the conditions of the message received by the smt for that particular monitor block. each of the message information bits is defined in the following section. 15 12 11 10 9 8 7 0 0 1 0 0 0 0 cha/ b rt-rt message information
59 s m mmit family 4.2.1.1 message information bits message information bits are provided as a means to supply more data on the message. in a rt-rt transfer, the information applie s to the complete message. each message information bit is defined below. 4.2.2 command words the next two locations in the smt monitor block are for command words. in non-rt-rt 1553 messages, only the first command word will be stored. however, in a rt-rt transfer, the first command word is the receive command and the second command word is the transmit command. 4.2.3 data pointer the fourth location in the smt monitor block is the data pointer. this pointer points to the first memory location to store the data words associated with the message for this block. note that the data associated with each individual message will be stored contiguously. this data structure allows the smt to store the specified number of data words. (note: in a rt-rt transfer, the smt uses the data pointer as the location in memory to store the transmitting data in the transfer.) 4.2.4 status words the next two locations in the smt monitor block are for status words. as the rt responds to the bc?s command, the corresponding status word will be stored in status word 1. however, in a rt-rt transfer, the first status word will be the status of the transmitting rt while the second status word will be the status of the receiving rt. 4.2.5 time-tag the seventh location in the smt monitor block is the time-tag associated with the message. the time-tag is stored into this location at the end of message processing (i.e., captured after the command is validated). 4.2.6 unused the last location in the smt monitor block is unused. bit number description 7 message error. this bit will be set if the monitor detects an error in either the command word, data words, or the rt?s status. 6 mode code without data. this bit will be set if the monitor detects that the command being processed is a mode code without data words. 5 broadcast. this bit will be set if the monitor detects that the command being processed is a broadcast message. 4 reserved. 3 time-out error. this bit will be set if the srt did not receive the proper number of data words, e.g., the number of data words received was less than the word count specified in the command word. 2 overrun error. this bit will be set if the srt received a word when none were expected or the number of data words received was greater than expected. 1 parity error. this bit will be set if a parity error has occurred on the data words or the rt?s status word. 0 manchester error. this bit will be set if a manchester error has occurred on either the data words or the rt?s status word.
60 s m mmit family 4.3 monitor block chaining the host determines the first monitor block by setting the start address in the initial monitor block pointer register (register 11). figure 13 shows the smt monitor blocks as the blocks execute in a contiguous fashion (monitor block count register 13 = 5). 4.4 memory architecture figure 14 shows the monitor blocks, data locations, and the interrupt log list as separate entities within memory. the configuration shows that the first block of memory is allocated for the monitor blocks. notice that register 11 points to the initial monitor block location, register 12 points to the initial data location, register 5 points to the interrupt log, and register 13 contains the monitor block count. after execution begins, the smt will build command blocks and store data words until the count reaches zero. when the count reaches zero, the smt will simply wrap back to the initial values and start again. figure 14. memory architecture for monitor mode initial monitor command block pointer register monitor (memory) data storage initial monitor data pointer register interrupt (memory) msg info word cmd words data ptr status words time-tag unused reg 11 memory int info word monitor block reg 12 interrupt log list pointer register reg 5 msg info word cmd words data ptr status words time-tag unused msg info word cmd words data ptr status words time-tag unused monitor block #4 monitor block #1 monitor block #2 monitor block #3 monitor block #6 monitor block #5 figure 13. monitor block structuring monitor block count = 5 monitor block count = 4 monitor block count = 3 monitor block count = 2 monitor block count = 1 monitor block count = 0
61 s m mmit family 4.5 message processing to process messages, the smt uses data supplied in the internal registers along with external memory. the smt uses eight external memory locations for each message called a monitor block. the monitor block is updated at the end of command processing. the following paragraphs discuss the monitor block in detail. the s m mmit features two different modes of transferring data to ram: buffer and non-buffer. the user selects the buffer or non-buffer transfer mode by setting the bufr bit (bit 6) in the control register. see sections 9.1.5 or 9.2.3 for additional information. the host or subsystem controlling the smt allocates memory spaces for each monitor block. the top of the monitor blocks can reside at any address location. initialized by the host, the smt is linked to the monitor block via the initial monitor block pointer register and the monitor block counter register contents. each monitor block contains a message information word, command word 1, command word 2, data pointer, status word 1, status word 2, and time-tag. refer to sections 4.2.1 - 4.2.6 for a full description of each location. the message information word allows the smt to tell the host or subsystem on which bus the command was received, whether the message was a rt-rt transfer, and conditions associated with the message. the smt also stores each command word associated with the message into the appropriate location. for normal 1553 commands, only the first command word location will contain data. for rt-rt commands, the second command word location will contain data, and bit 8 in the message information word will be set. for each command, the data pointer determines where to store data words. the smt stores data sequentially from the top memory location. the smt also stores each status word associated with the message into the appropriate location. for normal 1553 commands, only the first status word location will contain data. for rt-rt commands, the second status word location will contain data.the smt begins monitoring after control register bit 15=1 (i.e., assertion of stex). after reception, the smt begins post-processing. the smt performs a dma burst during post-processing. an optional interrupt log entry is performed after a monitor block is entered. monitor time-out: mil-std-1553a = 9 m s mil-std-1553b = 15 m s see section 5, enhanced s m mmit family operation for additional information. 4.5.1 error condition message processing when the monitor detects an error condition in either the command word, data words, or the rt?s status, the monitor block will not store the data. the monitor block counter increments. the initial message data pointer remains constant. the monitor block pointer increments. message information bits of the monitor block are changed to reflect the error. an interrupt is given indicating a message has occurred. see section 4.2.1.1 for additional information. 4.6 remote terminal/monitor terminal operation for applications that require simultaneous remote terminal and monitor terminal operations, the s m mmit should be configured as both a remote terminal (srt) and monitor terminal (smt). this feature allows the srt to communicate on the bus for one specific address and the smt to monitor the bus for other specific addresses. configuration as both smt and srt precludes the s m mmit from monitoring its own remote terminal address. when the s m mmit is configured as both srt and smt, the srt has priority over the smt. for example, commands to the srt will always take priority over monitoring functions for the smt. the examples below describe what happens if the srt is defined as terminal address 1 and the smt is to monitor terminal address 12. example 1: in this example, the smt will decode the first command on bus a, realize the message is for terminal address 12, and start monitoring the message. however, as soon as the srt realizes the second command on bus b is to terminal address 1, the srt will take priority and begin srt message processing. example 2: bus a bus b cmd/ta =12 cmd/ta =1 bus a bus b cmd/ta =1 cmd/ta =12
62 s m mmit family in example 2, the srt will decode the first command on bus a, realize the message is for terminal address 1, and start message processing. as the message on bus b is received, the s m mmit will realize it is to terminal address 12, but since the srt has priority the smt will not switch to the monitor mode. the above examples also apply to a rt-rt message. for example, if the first command in a rt-rt transfer matches the terminal address of the srt, the entire message will be processed by the srt (message 1). however, if the first command in a rt-rt transfer matches the terminal address of the smt and the second command matches the terminal address of the srt, the srt will take priority and process the message (message 2). below is a rt-rt message example. 4.7 mil-std-1553a operation to maximize flexibility, the s m mmit has been designed to operate in many different systems which use various protocols. specifically, two of the protocols that the s m mmit may be interfaced to are mil-std-1553a and mil-std-1553b. to meet these protocols, the s m mmit may be configured through an external pin or through control register bits (depending on the state of the lock pin). table 6. mil-std-1553a operation when configured as a mil-std-1553a monitor, the s m mmit will operate as follows: looks for the rt response within 9 m s (see section 5, enhanced s m mmit family operation); defines all mode codes without data; defines subaddress 00000 as a mode code. message 1 message 2 cmd/ta =1 cmd/ta =12 cmd/ta =12 cmd/ta =1 a/ b std (pin) result 0 1553b response, 1553b standard 1 1553a response, 1553a standard
s m mmit family - 63 5.0 enhanced s m mmit family operation the following describes the enhanced s m mmit features. 5.1 message time-out programmable bus controller and monitor time-out feature allows for the implementation of extended buses. bit 9 of the control register determines the remote terminal no response time period. during mil-std-1553b operation, the program- mable time-out occurs at either 14 m s or 30 m s. in mil-std- 1553a mode, time-out occurs at either 9 m s or 21 m s. see figure 15. 5.2 dma time-out dma time-out, in the bus controller mode of operation, is 16 m s (t b , t a ). the s m mmit architecture times all dma cycles to ensure that memory access timing supports message pro- cessing. excessive memory access delays result in a dma time-out condition. in the event of dma time-out, the s m mmit ceases message processing and generates an inter- rupt if enabled. the s m mmit e and s m mmit lxe/dxe specify the dma time-out period per ac electrical character- istic t b . the s m mmit xte specifies the dma time-out per ac electrical characteristic t a . see figure 38 for t b and figure 50 for t a . 5.3 circular buffers the s m mmit family circular buffer simplifies the software service of remote terminals implementing bulk or periodic data transfers. the enhanced s m mmit architecture allows the user to select one of two circular buffer modes. the user selects the preferred mode, at start-up, by writing to control register bits 7 and 8. the control register bits allow for the decode of three unique modes. table 7 reviews mode selec- tions. 5.3.1 mode number 0 remote terminal index or ping-pong operation, non- enhanced s m mmit, the user programs bits 7 and 8 to logical zero. operation is per sections 2.2 and 2.3 (default state). 5.3.2 mode number 1 remote terminal buffer 1, enhanced s m mmit operation, the user programs bit 7 to 0 and bit 8 to 1. the s m mmit merges transmit or receive data into a circular buffer along with mes- sage information. for each valid receive message, the s m mmit enters a message information word, time-tag word, and data word(s) into a unique receive circular buffer. for each valid transmit message, the s m mmit enters a message infor- mation word and time-tag word into reserved memory loca- tions within the transmit circular buffer. the s m mmit automatically controls the wrap around of circular buffers. two pointers define circular buffer length: top of buffer and bottom of buffer. user specifies the top of buffer (i.e., top address (ta 16 )) by writing a value into the second word of a unique mode code or subaddress descriptor block. the user defines the bottom of the buffer (i.e., bottom address (ba 16 )) by writing to the fourth word of that unique descriptor block. both the ta 16 and ba 16 remain static during message process- control register figure 15. programmable bus controller time-out bit 9: bus controller and monitor only time-out logical 0 time-out occurs at 14 m s logical 1 time-out occurs at 30 m s table 1: table 7. enhanced mode of operation mode number bit 7 bit 8 0 0 0 1 0 1 x 1 0 2 1 1
s m mmit family - 64 ing. the third word in the descriptor block identifies the cur- rent address (i.e., last accessed address plus one). the circular buffer wraps to the top address after completing a message that results in ca 16 being greater than or equal to ba 16 . if ca 16 increments past ba 16 during intra-message processing, the s m mmit will access memory (read or write) address locations past ba 16 . delimit all circular buffer boundaries with at least 34 address locations. each subaddress and mode code, both transmit and receive, has a unique circular buffer assignment. the s m mmit decodes the command word t/r bit, subaddress/mode field, and word count/mode code field to select a unique descriptor block which contains ta 16 , ca 16 , and ba 16 . for receive messages, the s m mmit stores the message infor- mation word into address location ca 16 , the time-tag word into ca 16 + 1 16 , and the data into the next ?n 16 ? locations starting at address ca 16 +2 16 . for each transmit command, the s m mmit stores the message information word into address location ca 16 and time-tag word into location ca 16 + 1 16 . retrieval of data for transmission starts at address location ca 16 + 2 16 . when entering multiple transmit command data packets into the circular buffer, delimit each data packet with two reserved memory locations. the s m mmit enters the mes- sage information word and time-tag word into the delimiting memory locations. 5.3.3 mode number 2 circular buffer 2, enhanced s m mmit operation, the user pro- grams control register bit 7 to 1 and bit 8 to 1. the s m mmit separates message data and message information into unique circular buffers. the separation of data from message informa- tion simplifies the software that loads and unloads data from the buffers. each subaddress and mode code, both transmit and receive, has a unique pair of circular buffers. the s m mmit decodes the command word t/ r bit, subaddress/mode field, and word count/mode code field to select a unique descriptor block which contains ta 16 , ca 16 , and message information buffer (mib). control the wrap-around of both the data and message circular by specifying the number of messages before wrap-around occurs. the second word entered into the descriptor block determines the top of the data buffer (ta 16 ). the third word in the descriptor block identifies the current position (ca 16 ) in the buffer (i.e., last accessed address plus one). the fourth word in the descriptor block identifies the mib?s starting loca- tion and current position. the mib contains time-tag and message information words for each message transacted on the bus. the data buffer and message information word buffer wrap around after processing a pre-determined number of messages. each subaddress and mode code, both transmit and receive, has a unique data buffer and mib assignment. 5.4 ping-pong handshake the enhanced s m mmit provides a software handshake which indicates the enable and disable of buffer ping-pong operation. during remote terminal operation, the s m mmit asynchronous ping-pongs between two subaddress or mode code data buff- ers. to perform buffer service, the application software must freeze the remote terminal?s access to a single buffer. the s m mmit?s ping-pong enable/disable handshake allows the application software to asynchronously freeze (i.e., disable ping-pong operation) the remote terminal to a single buffer. 5.5 circular buffer mode #1 to implement circular buffer 1?s architecture, the four word descriptor block and control register are different than in the mode #0. bits 15 through 8 of the control word are don?t care. the second word of the descriptor block defines the buffer?s starting or top address (ta 16 ). the ta pointer remains static during message processing. the fourth entry into the descrip- tor block identifies the buffer?s bottom address (i.e., ba 16 ) and also remains static during message processing. the third descriptor block word represents the current address (i.e., ca 16 ) in the buffer and is dynamic. if the s m mmit observes no message error conditions, the ca 16 pointer updates at the end of message processing. the application software reads the dynamic ca 16 pointer to determine the current bottom of the buffer. first, a review of receive message processing. the s m mmit begins all message processing by reading a unique descriptor block after reception and validation of a subaddress or mode code command word. the s m mmit internally increments the ca 16 pointer to store the receive data word(s). after message processing completes, the s m mmit stores the message infor- mation word and time-tag word into the circular buffer preced- ing the message data. at the end of message processing, the s m mmit updates ca 16 (if no errors detected). for ca 16 larger than ba 16 storage of the next message begins at the address location pointed to by the ta 16 pointer, and ca 16 is made equal to ta 16 . if ca 16 is less than ba 16 , ca 16 points to the next available memory location in the buffer (i.e., ca 16 + 1). for transmit commands, the s m mmit begins transmission of data from memory location ca 16 + 2 16 . reserve the first two locations for the message information word and time-tag word. after message processing completes, the s m mmit enters the message information word and time-tag word into the circular buffer. at the end of message processing, the s m mmit updates ca 16 (if no errors detected). for ca 16
s m mmit family - 65 larger than ba 16 , storage of the next message begins at the address location pointed to by the ta 16 pointer, and ca 16 is made to equal ta 16 . if ca 16 is less than ba 16 , ca 16 points to the next available memory location in the buffer (i.e. ca 16 + 1). in this mode of operation, bits indx, nii and a/b of the descriptor control word and the ppen bit of the control reg- ister are don?t care. message information word bit 5 reflects the reception of broadcast message via the brd bit. the s m mmit generates a circular buffer empty/full interrupt when the buffer reaches the end (i.e., ca 16 greater than ba 16 ) and begins a new message at the top of the buffer. bit 8 of the mask register and bit 7 of the descriptor control word mask enables the generation of the full/empty interrupt. on the occurrence of either interrupt, the msg_int output asserts. figure 16 describes the relationship between ta 16 , ba 16 , and ca 16 . control register descriptor block control word ta ca ba circular buffer time-tag data words message information word bits 7 and 8 select circular buffer data words data words figure 16. circular buffer mode #1 message information word time-tag data words data words
s m mmit family - 66 5.6 circular buffer mode #2 to implement circular buffer 2?s architecture, the descriptor block and control register are different than in mode #0. bits 15 through 8 of the control word spec- ify the message information buffer (mib) length; the maximum mib length is 256. table 8 shows how the control word?s most significant bits select the depth of the mib. the control words eight most significant bits remain static during message processing. the second word of the descriptor block defines the top address (ta 16 ) of the data circular buffer. the ta 16 pointer remains static during message processing. the third descriptor word identifies the current address (i.e., ca 16 ) of the data circular buffer. the application soft- ware reads the dynamic ca 16 pointer to determine the current address of the data buffer. the s m mmit incre- ments the ca 16 pointer, at the end of message process- ing, until the mib buffer is full. when the mib wraps around, the s m mmit loads the ca 16 pointer with the ta 16 pointer. the fourth word in the descriptor block defines the top or base address of the message information buffer (i.e., mib) and the current mib address (i.e., offset from base address). the s m mmit enters the message information word and time-tag word into the mib, for each message, until the end of the mib is reached. when the mib reaches the end, the next message?s message informa- tion word and time-tag word is entered at the top of the mib. the mib pointer is a semi-static pointer. the s m mmit updates the current address field at the end of message processing. the base address field remains static. application software reads the current mib address to determine the number of messages processed since last service. the variable length mib requires the base address and current address field to also vary in length. table 8 displays the relationship between control word bits 15 through 8, mib length, mib base and current address fields. the current address field of the mib must begin on an even boundary. first is a review of receive message processing. the s m mmit begins all message processing by reading the descriptor block of the subaddress or mode code com- mand received (i.e., controlword, ta 16 , ca 16 , and mib). the s m mmit begins storage of data word(s) starting at the location contained in the ca 16 pointer. the s m mmit automatically updates the ca 16 pointer internally as message processing progresses. after receiving the correct number of data words, the s m mmit stores the message information word and time-tag word into the mib. at the end of message pro- cessing, the s m mmit updates ca 16 and mib current address field (caf). if caf equals the specified mib length, ca 16 is updated to ta 16 and the mib caf is reset to zero. if caf is less than the specified mib length, ca 16 and mib caf point to the next available memory location in each buffer. control word bits 15 to 8 specify the mib length. for transmit commands, the s m mmit begins transmis- sion of data from memory location ca 16 . after message processing completes, the s m mmit enters the message information word and time-tag word into the mib. at the end of message processing, the s m mmit updates ca 16 and the mib caf. if caf equals the specified mib length, ca 16 is updated to ta 16 and the mib caf is reset to zero. if caf is less than the specified mib length, ca 16 and mib caf point to the next available memory location in each buffer. in this mode of operation, bits indx, nii and a/b of the descriptor control word and the ppen bit of the command register are don?t care. the brd bit is added to the message information word bit 5. the s m mmit generates a circular buffer empty/full interrupt when the mib reaches the end and begins a new message at the top of the buffer. bit 8 of the mask register and bit 7 of the descriptor control word mask and enable the generation of the full/empty interrupt. on the occurrence of either interrupt, the msg_int output asserts. figure 17 describes the relationship between ta 16 , ca 16 , and mib.
s m mmit family - 67 table 8. control word and mib length control word bits (15:8) length of mib mib pointer base and caf [base address][caf] = memory location bit positions 15 - 14 - 13 - 12 - 11 - 10 - 9 - 8 - 7 - 6 - 5 - 4 - 3 - 2 - 1 - 0 ff 128 [----------base address ------------------------------][---------------------------caf--------------------] 7f 64 [------------base address------------------------------------][--------------------caf--------------------] 3f 32 [---------------base address----------------------------------------][-----------------caf----------------] 1f 16 [------------------base address------------------------------------------- ][---------------caf-----------] 0f 8 [---------------------base address------------------------------------------------][----------caf---------] 07 4 [-----------------------base address-----------------------------------------------------][-----caf-------] 03 2 [-------------------------base address---------------------------------------------------------][---caf---] 01 1 [---------------------------base address-------------------------------------------------------------][caf]
s m mmit family - 68 5.7 ping-pong enable/disable handshake prior to starting remote terminal operation, enable the buffer ping-pong feature by writing a logical 1 to bit 2 of the control register. during ping-pong operation, the remote terminal ping-pongs between the two data buffers, for each subaddress or mode code, on a message by message basis. each unique mil-std-1553 subaddress and mode code is assigned two data buffer locations (a and b). the remote terminal retrieves data from a buffer or stores data into a buffer depending on the message type (i.e., transmit or receive command). during ping-pong operation, the remote terminal determines the active subaddress or mode code buffer at the beginning of message processing, the remote terminal complements bit 2 of the descriptor control word to access the alternate buffer on the following message (i.e., ping-pong). see figure 18 for ping-pong buffer flow chart. to off-load or load the subaddress and mode code buffers without collisions (e.g., remote terminal writing and applica- tion software reading the same buffer), the application soft- ware must disable ping-pong operation (i.e., freeze the remote terminal access to a single buffer, either a or b). disabling ping-pong operation allows the application software to off- load or load the alternate buffer while the remote terminal con- tinues to use the active buffer. to implement this architecture, ping-pong operation must enable and disable asynchronously via software with feedback to indicate that buffer ping-pong- ing is truly disabled. second, unique subaddress and mode code flags indicate which buffer is active. each unique subad- dress and mode code is assigned a flag which indicates the active buffer. bits 7 and 8 select circular buffer 2 control register descriptor block 15 8 buffer size control word ta ca mib data buffer message information word time-tag figure 17. circular buffer mode #2 mib
s m mmit family - 69 use buffer b buffer usage descriptor use buffer a read descriptor complete msg processing, update descriptor buffer to a, a/ b =0 descriptor a/ b =1 set a/ b = 1 complete msg processing, update descriptor buffer to b, set a/ b = 0 receive 1553 cmd command valid yes no figure 18. ping-pong buffer flow chart
s m mmit family - 70 to begin the process of off-loading or loading the remote ter- minal?s subaddress and/or mode code buffers, when using the ping-pong feature, the application software performs the fol- lowing sequence: disables ping-pong operation, determines the active buffer, services the alternate buffer, enables ping- pong operation. the application software disables ping-pong operation by writing a logical zero to control register bit 2. the disable of ping-pong operation is acknowledged by bit 9 of the control register. bit 9 of the control register acknowledges the ping- pong disable by transitioning from a logical one to a logical zero. the application software interrogates bit 2 of each descriptor control word to determine the active buffer on a subaddress or mode code basis. if bit 2 is a logical zero, the remote terminal uses buffer a and the application software off-loads or loads buffer b. if bit 2 is a logical one, the remote terminal uses buffer b and the application software off-loads or loads buffer a. figure 19 displays control register bits for ping-pong enable/disable and acknowledge. the application software enables ping-pong operation by writ- ing a logical one to control register bit 2. the enable of ping- pong operation is acknowledged by bit 9 of the control regis- ter. bit 9 of the control register acknowledges the ping-pong enable by transitioning from a logical zero to a logical one. 15 9 2 0 logical 0 ping-pong logical 1 ping-pong figure 19. ping-pong handshake enabled disabled control register enable/disable acknowledge logical 0: disable acknowledge logical 1: enable acknowledge
s m mmit family - 71 6.0 i n t e r r u p t a r c h i t e c t u r e 6.1 s m mmit e & s m mmit lxe/dxe the s m mmit e & s m mmit lxe/dxe interrupt architecture involves three internal registers, an interrupt log list and two interrupt outputs. the three internal registers include a pending interrupt register, interrupt mask register, and interrupt log list register. see figure 20 and register descriptions for additional information. the pending interrupt register contains information that identifies the events generating the interrupts. the interrupt mask register allows the user to mask or disable the generation of interrupts. the interrupt log list register contains the base address of a 32-word interrupt ring buffer. two interrupt outputs signal the occurrence of an interrupt event. the interrupt architecture differentiates interrupts as either a hardware interrupt ( yf_int ) or message interrupt ( msg_int ). the yf_int interrupt bits are stored in the upper four bits of the pending interrupt register and the bit word register. these four interrupts must be processed as they occur since they are not stored in the interrupt log list. note: if the pending interrupt register is not cleared after the first yf_int, the setting of other yf_int bits will not result in a yf_int pulse. the msg_int bits are stored in the pending interrupt register. these interrupts are entered into the interrupt log list, if the interrupt log list is enabled. the s m mmit e & s m mmit lxe/dxe interrupt architecture also allows the entry of 16 interrupts into a 32-word ring buffer. the s m mmit e & s m mmit lxe/dxe automatically handles the interrupt logging overhead. each interrupt generates two words of information to assist the host or subsystem when processing interrupts. the interrupt identification word (iiw) identifies the type(s) of interrupt that occurred. the interrupt address word (iaw) identifies the interrupt source via a 16-bit address. the s m mmit e & s m mmit lxe/dxe asserts one of two outputs, msg_int or yf_int , to signal the host or subsystem that an interrupt event occurred. the yf_int may occur at any time. the msg_int asserts after the final dmack negation associated with the storage of the iiw and iaw. 6.1.1 interrupt identification word (iiw) the interrupt identification word (iiw) is a 16-bit word identifying the interrupt type(s). the format is similar to the pending interrupt register. the host or subsystem reads the iiw to determine which interrupt event occurred. the bit description for the iiw is provided in table 9. 6.1.2 interrupt address word (iaw) the interrupt address word (iaw) is a 16-bit word that identifies the interrupt source. depending on the mode of operation (i.e., srt, sbc, or smt), the iaw has different meanings. in the srt mode of operation, the iaw identifies the subaddress or mode code descriptor that generated the interrupt. for the sbc mode of operation, the iaw points to the command block addressed when the interrupt occurred. in the smt mode of operation, the iaw marks the monitor counter count when the interrupt occurred. the host uses the iaw with the initial monitor command block pointer register to determine the monitor command block that generates the interrupt. when the smt is operating concurrently with the srt, the host must determine if the iaw contains information for the srt or smt. the determination is made by comparing the contents of the iaw base address with the descriptor base address. if a match occurs, then the iaw contains a subaddress or mode code identifier. if no match occurs, the iaw contains monitor counter information. 6.1.3 interrupt log list address the interrupt log list resides in a 32-word ring buffer. the host or subsystem defines the location buffer, within a 64k x 16 memory space, via the interrupt log list register (register 5). restrict the ring buffer address to a 32-word boundary. during initialization the host or subsystem writes a value to the interrupt log list pointer register, initializing the least significant five bits to a logic zero. the most significant 11 bits determine the base address of the buffer. the s mmm it & s mmm it lxe/dxe increments the ring buffer pointer on the figure 20. pending interrupt and mask register 15 12 11 yf_int bits msg_int bits 0
s m mmit family - 72 occurrence of the first interrupt, storing the iiw and iaw at locations 00000 and 00001 respectively. the s mmm it e & s mmm it lxe/dxe logs ensuing interrupts sequentially into the ring buffer until interrupt number 16 occurs. the s mmm it e & s mmm it lxe/dxe enters interrupt 16?s iiw in buffer location 11110 and the iaw at location 11111. the ring wraps- around at a value of 11111. the s mmm it e & s mmm it lxe/dxe increments the ring buffer pointer as interrupts occur. the least significant five bits of the interrupt log list pointer register reflect the ring buffer pointer value. figure 21 shows the ring buffer architecture. the host or subsystem reads the ring buffer pointer value to determine the number of interrupts that have occurred. by extracting the least significant five bits from the interrupt log list register and logically shifting the data once to the right, the host or subsystem determines the number of interrupt events. table 9. interrupt information word bit number mnemonic description 15-12 n/a not applicable. 11 merr message error interrupt (all modes). 10 subad subaddress accessed interrupt (srt). 9 bdrcv broadcast command received interrupt (srt). 8 ixeq0 index equal zero interrupt (srt). 7 ilcmd illegal command interrupt (srt). 6 n/a not applicable. 5 eol end of list (sbc). 4 illcmd illogical command (sbc). 3 illop illogical opcode (sbc). 2 rtf retry fail (sbc). 1 cba command block accessed (sbc). 0 mbc monitor block count equal zero (smt).
s m mmit family - 73 figure 21. interrupt ring buffer base address + 00000 base address + 00001 base address + 00010 base address + 00011 base address + 00100 base address + 00101 base address + 00110 base address + 00111 base address + 01000 base address + 01001 base address + 01010 base address + 01011 base address + 01100 base address + 01101 base address + 01110 base address + 01111 base address + 10000 base address + 10001 base address + 10010 base address + 10011 base address + 10100 base address + 10101 base address + 10110 base address + 10111 base address + 11000 base address + 11001 base address + 11010 base address + 11011 base address + 11100 base address + 11101 base address + 11110 base address + 11111 iiw #1 iiw #2 iiw #3 iiw #4 iiw #5 iiw #6 iiw #7 iiw #8 iiw #9 iiw #10 iiw #11 iiw #12 iiw #13 iiw #14 iiw #15 iiw #16 iaw #16 iaw #1 iaw #2 iaw #3 iaw #4 iaw #5 iaw #6 iaw #7 iaw #8 iaw #9 iaw #10 iaw #11 iaw #12 iaw #13 iaw #14 iaw #15 interrupt log list address register contents interrupt log list address register contents ring-buffer pointer
s m mmit family - 74 6.2 s m mmit xte the s m mmit xte?s interrupt architecture involves three internal registers, an interrupt log list, two interrupt outputs, and two interrupt acknowledges. the three internal registers include a pending interrupt register, interrupt mask register, and interrupt log list register. see figure 20 and register descriptions for additional information. the pending interrupt register contains information that identifies the events generating the interrupts. the interrupt mask register allows the user to mask or disable the generation of interrupts. the interrupt log list register contains the base address of a 32- word interrupt ring buffer. two interrupt outputs signal the occurrence of an interrupt event. the interrupt architecture differentiates interrupts as either a hardware interrupt ( yf_int ) or message interrupt ( msg_int ). the user programs the interrupt outputs as either pulsed outputs or level outputs depending on system requirements. assertion of the yf_int interrupt signals a hardware failure condition. failures include dma time-out, wrap-around self- test, terminal address parity, or built-in test (bit). yf_int failures are reflected in the four most significant bits of the pending interrupt register. the yf_int output asserts on the occurrence of a failure. assertion of the msg_int interrupt signals a message related event has occurred. msg_int events are reflected in the 12 least significant bits of the pending interrupt register. the msg_int asserts after message processing is complete. the interrupt architecture allows for the entry of 16 interrupts into a 32-word ring buffer (see figure 21). the s m mmit xte automatically handles the interrupt logging overhead. each interrupt generates two words of information to help the host or subsystem perform interrupt processing. the interrupt identification word (iiw) identifies the type(s) of interrupt that occurred. the interrupt address word (iaw) identifies the interrupt source (e.g., subaddress or command block) via a 16- bit address. the s m mmit xte?s interrupt outputs are user programmable. the user can select either pulsed interrupt outputs or level sensitive outputs. in the level mode of operation, assertion of either input (i.e., yf_ack or msg_ack ) negates the respective interrupt output (i.e., yf_int or msg_int ). the state of msel(4) selects the mode of operation, table 10 reviews operation. table 10. msel(4) operation 6.2.1 interrupt identification word (iiw) the interrupt identification word (iiw) is a 16-bit word identifying the interrupt type(s). the format is similar to the pending interrupt register. the host or subsystem reads the iiw to determine which interrupt event occurred. the bit descriptor for the iiw is provided in table 9. 6.2.2 interrupt address word (iaw) the interrupt address word (iaw) is a 16-bit word that identifies the interrupt source. depending on the mode of operation (i.e., srt, sbc, or smt), the iaw has different meanings. in the srt mode of operation, the iaw identifies the subaddress or mode code descriptor that generated the interrupt. for the sbc mode of operation, the iaw points to the command block addressed when the interrupt occurred. in the smt mode of operation, the iaw marks the monitor counter count when the interrupt occurred. the host uses the iaw with the initial monitor command block pointer register to determine the monitor command block that generates the interrupt. when the smt is operating concurrently with the srt, the host must determine if the iaw contains information for the srt or smt. the determination is made by comparing the contents of the iaw base address with the descriptor base address. if a match occurs, then the iaw contains a subaddress or mode code identifier. if no match occurs, the iaw contains monitor counter information. 6.2.3 interrupt log list address the interrupt log list resides in a 32-word ring buffer. the host or subsystem defines the location buffer, within a 32k x 16 memory space, via the interrupt log list register (register 5). restrict the ring buffer address to a 32-word boundary. msel(4) yf_int msg_int yf_ack msg_ack 0 pulse output tied high 1 level output active low
s m mmit family - 75 during initialization the host or subsystem writes a value to the interrupt log list pointer register, initializing the least significant five bits to a logic zero. the most significant 11 bits determines the base address of the buffer. the s m mmit xte increments the ring buffer pointer on the occurrence of the first interrupt, storing the iiw and iaw at locations 00000 and 00001 respectively. the s m mmit xte logs ensuing interrupts sequentially into the ring buffer until interrupt number 16 occurs. the s m mmit xte enters interrupt 16?s iiw in buffer location 11110 and the iaw at location 11111. the ring wraps- around at a value of 11111. the s m mmit xte increments the ring buffer pointer as interrupts occur. the least significant five bits of the interrupt log list pointer register reflect the ring buffer pointer value. figure 21 shows the ring buffer architecture. the host or subsystem reads the ring buffer pointer value to determine the number of interrupts that have occurred. by extracting the least significant five bits from the interrupt log list register and logically shifting the data once to the right, the host or subsystem determines the number of interrupt events.
s m mmit family - 76 7.0 a u t o -i n i t i a l i z a t i o n 7.1 s m mmit e & s m mmit lxe/dxe the s m mmit e & s m mmit lxe/dxe auto-initialization feature allows autonomous operation. the s m mmit e & s m mmit lxe/dxe will automatically configure itself for operation from nonvolatile 16-bit wide memory (prom, rom, e 2 prom, eprom, etc.). the configuration sequence begins after the negation of input pin mrst , if autoen is enabled. for each mode of operation, the auto-initialization function is different. the following section outlines the auto-initialization feature for each mode of operation. 7.1.1 srt auto-initialization during auto-initialization, the s m mmit e & s m mmit lxe/ dxe loads all internal registers and transfers the descriptor space into ram. initialize registers not used during srt operation to 0000 (hex). the srt must have 32 memory locations allocated for register data. following register initialization, the s m mmit e & s m mmit lxe/dxe reads the descriptor from rom and enters the descriptor into ram. the starting address for the descriptor is read from the descriptor pointer register. the s m mmit e & s m mmit lxe/dxe internally generates all address information required for auto-initialization. the s m mmit e & s m mmit lxe /dxe requires 544 consecutive rom locations for initialization. the 544 memory locations include: 32 for internal register information, 256 for subaddress descriptor information, and 256 for mode code descriptor information. unused descriptor blocks should be initialized to four words of 0000 (hex). the srt accesses 544 consecutive memory locations in 32- word blocks. the srt arbitrates for the bus once. once access is granted, the srt reads 32 words from rom, then transfers the information into ram. the srt does not release the bus until all 544 rom locations are transferred. the srt does not respond to mil-std-1553 commands until initialization is complete, the start execution bit has been set, and the rt parity has been verified. after initialization, the srt can respond to mil-std-1553 commands. 7.1.2 smt auto-initialization smt auto-initialization requires only the loading of internal registers. registers not used during smt operation should be initialized to 0000 (hex). the smt requires allocation of 32 memory locations for register data. the s m mmit e & s m mmit lxe/dxe internally generates all address information for auto- initialization. when operating as a concurrent srt and smt, the s m mmit e & s m mmit lxe/dxe loads all internal registers for both srt and smt modes of operation. the device then transfers the descriptor from rom to ram. 7.1.3 sbc auto-initialization during auto-initialization the s m mmit e & s m mmit lxe/ dxe loads all internal registers and transfers the command block(s) into ram. registers not used during sbc operation should be initialized to 0000 (hex). the sbc requires the allocation of 32 memory locations for register data. following register initialization, the s m mmit e & s m mmit lxe/dxe reads command block(s) information from rom and enters them into ram. the starting address for the command block(s) is read from the command block pointer register. the s m mmit e & s m mmit lxe/dxe internally generates all address information for auto-initialization. the sbc continues to read command blocks from rom until the command block initialization count register decrements to zero. 7.1.4 auto-initialization hardware to enable the auto-initialization function, assert the autoen pin before the rising edge of mrst . the de-assertion of mrst signals the beginning of the auto-initialization sequence. the assertion of output romen enables the rom for data access. output romen remains active until the completion of auto- initialization. simultaneous with the assertion of romen , the s m mmit e & s m mmit lxe/dxe arbitrates for the bus by asserting dmar . upon completion of auto-initialization, the s m mmit e & s m mmit lxe/dxe asserts the ready output pin. output ready asserts after negation of dmack . at this time, the s m mmit e & s m mmit lxe/dxe is prepared for operation, if it has been started (i.e., stex=1). the s m mmit e & s m mmit lxe/dxe is idle until reception of a valid command word, or begins command block processing. the rom?s starting location is 0000 (hex), ram and rom are overlaid by using the romen output pin as a rom device select or output enable. figures 22a and 22b show examples of the relative timing associated with an auto-initialization sequence.
s m mmit family - 77 mrst autoen romen dma activity ready mrst autoen rta(4:0) rtpty lock 10ns (min) 5.0 m s (min) note: 1. utmc strongly recommends that these inputs remain static until the assertion of ready . valid valid valid valid romen 5.0 m s (max) dmar valid a/ b std and msel(1:0) 5.0 m s (max) figure 22a. auto-initialization timing figure 22b. auto-initialization dma sequence
s m mmit family - 78 7.2 s m mmit xte the s m mmit xte auto-initialization feature allows autonomous operation. the s m mmit xte will automatically configure itself for operation from nonvolatile byte-wide memory (prom, rom, e 2 prom, epprom, etc.). the configuration sequence begins after the negation of input pin mrst , if autoen is enabled. for each mode of operation, the auto-initialization function is different. the following sections outline the auto-initialization feature for each mode of operation. 7.2.1 srt auto-initialization during auto-initialization, the s m mmit xte loads all internal registers and transfers the descriptor space into ram. initialize registers not used during srt operation to 0000 (hex). the srt must have 64 memory locations allocated for register data. following register initialization, the s m mmit xte reads the descriptor from rom and enters the descriptor into ram. the starting address for the descriptor is read from the descriptor pointer register. the s m mmit xte internally generates all address information required for auto-initialization. the s m mmit xte requires 1088 consecutive rom locations for initialization. the 1088 memory locations include: 64 for internal register information, 512 for subaddress descriptor information, and 512 for mode code descriptor information. unused descriptor blocks should be initialized to four words of 0000 (hex). the srt accesses 1088 consecutive memory locations in 64- word blocks. once access is granted, the srt reads words from rom, then transfers the information into ram. the srt does not respond to mil-std-1553 commands until initialization is complete, the start execution bit has been set, and the rt parity has been verified. after initialization, the srt can respond to mil-std-1553 commands. 7.2.2 smt auto-initialization smt auto-initialization requires only the loading of internal registers. registers not used during smt operation should be initialized to 0000 (hex). the smt requires allocation of 64 memory locations for register data. the s m mmit xte internally generates all address information for auto- initialization. when operating as a concurrent srt and smt, the s m mmit xte loads all internal registers for both srt and smt modes of operation. the device then transfers the descriptor from rom to ram. 7.2.3 sbc auto-initialization during auto-initialization the s m mmit xte loads all internal registers and transfers the command block(s) into ram. registers not used during sbc operation should be initialized to 0000 (hex). the sbc requires the allocation of 64 memory locations for register data. following register initialization, the s m mmit xte reads command block(s) information from rom and enters them into ram. the starting address for the command block(s) is read from the command block pointer register. the s m mmit xte internally generates all address information for auto- initialization. the sbc continues to read command blocks from rom until the command block initialization count register decrements to zero. 7.2.4 auto-initialization hardware an external auto-initialization bus allows configuration of s m mmit xte without host intervention. auto-initialization is ideal for low cost remote sensing applications where a host microprocessor or microcontroller is not required. to enable the auto-initialization function, assert the autoen pin prior to the rising edge of mrst . the assertion of mrst signals the beginning of the auto- initialization sequence. the s m mmit xte enables the boot memory by asserting the ecs output. the s m mmit xte accesses up to 8k x 8 words via the auto-initialization bus. table 8 reviews the memory requirements for s m mmit xte auto- initialization. table 11. auto-initialization memory requirements note: 1. n equals the number of command blocks. mode memory (x8) srt 1088 smt 64 sbc 64 + [n x (16)] 1
s m mmit family - 79 to interface to slower non-volatile memory the auto- initialization read cycle period is programmable. the user selects between zero and seven wait states per read. a wait state is equal to 82ns. the user programs the read cycle duration via inputs ec(2:0). the s m mmit xte latches inputs ec(2:0) on the rising edge of mrst . table 12 reviews the possible combinations of wait-states. figures 23a and 23b show a system configuration along with typical auto-initialization read cycles. following completion of an auto-initialization sequence the s m mmit xte asserts the ready output. table 12. programmable wait-state ec(2:0) 2 number of wait-states 000 0 001 1 010 2 011 3 100 4 101 5 110 6 111 7 figure 23a. auto-initialization system configuration s m mmit xte autoen ecs ed(7:0) ea(12:0) auto-init memory a(12:0) d(7:0) cs
s m mmit family - 80 figure 23b. auto-initialization read cycle 24mhz ea(12:0) ed(7:0) ecs autoen mrst 5 m s max zero wait-state read cycle address data valid 24mhz ea(12:0) ed(7:0) ecs autoen mrst two wait-state read cycle address data valid ec(2:0) ec(2:0) valid valid 5 m s max note: two bytes are read on each ecs cycle using only an address transition (at). data valid address data valid address
s m mmit family - 81 8.0 testability the following sections review the built-in test capabilities of the s m mmit family. the s m mmit family ranges from the simple s m mmit e to the complex s m mmit xte. the varying complexity results in slightly different test techniques to exercise each product type. table 13 is a list of the various components that comprehend each of the different s m mmit product. a s m mmit product?s built-in test (bit) varies depending on the product?s internal component mix and the bit initiating sequence. bit?s execution time will also vary depending on the number of internal components under test. table 14 reviews the various bit initiation sequences and the components that the sequence tests along with bit execution times. notes: 1. the transceiver is tested with the data wrap-around feature of the s m mmit family. see sections 2.1.5, 3.1.5, 4.1.5. 2. control register write of 4000 16 . before initiating memory test, reset the s m mmit xte by asserting mrst . 3. remote terminal mode of operation, bit initiated after reception of mode code command. 4. bus controller mode of operation, bit initiated after the fetch of a command block containing an initiate bit op-code. 5. s m mmit test 1ms. memory test 70ms. table 2: table 13. s m mmit family internal component list product protocol die transceivers memory mmu s m mmit e yes no no no s m mmit lxe yes yes no no s m mmit dxe yes yes no no s m mmit xte yes yes yes yes table 3: table 14. bit initiation initiation type protocol die transceivers 1 memory mmu execution time 2 cpu initiated 2 yes no yes no 1ms/70ms mode code initiated 4 yes no no no 1ms op-code initiated 5 yes no no no 1ms jtag 1149.1 yes no no yes n/a jtag/runbist yes no no no 1ms
s m mmit family - 82 9.0 s y s t e m c o n f i g u r a t i o n 9.1 s m mmit e & s m mmit lxe/dxe 9.1.1 transmitter/receiver interface the s m mmit manchester ii encoder/decoder interfaces directly with the ut63m100 series bus transceiver, using ta- ta and ra- ra signals for channel a, and tb- tb and rb- rb signals for channel b. see appendix 1 for additional information on utmc transceivers. the s m mmit also provides timerona and timeronb output signals to assist in meeting the mil-std-1553b fail-safe timer requirements (see figures 24a and 24b). reference section 10 for s m mmit lxe/ dxe serial bus interface information. rxout rxout txin txin txinhb txinhb rxout rxout utmc ut63m100 series s m mmit ut69151 ra ra rb rb txin txin ta ta timeron timero tb tb figure 24b. s m mmit transceiver interface diagram host subsystem addr(15:0) data(15:0) control ut63m100 series 1553 transceiver 1553 bus a s m mmit ut69151 1553 bus b figure 24a. s m mmit general system diagram
s m mmit family - 83 9.1.2 register transfers the host?s or subsystem?s access to the s m mmit e & s m mmit lxe/dxe internal registers is similar to its access to ram. after gaining control of the memory bus, the host supplies address information to bidirectional address bus pins a(4:0). after supplyi ng the address information, the host asserts s m mmit e & s m mmit lxe/dxe inputs cs and rd/ wr to designate a register access and the type of access. the memory access terminates on the negation of cs . for more information on register cycles refer to the timing diagrams and ac electrical specifications in section 20. for register utilization versus mode of operation see table 15. note: modifying (i.e., writing) internal registers is not recommended while the s m mmit e & s m mmit lxe/dxe is processing messages (i.e., teract active). the only exception occurs when the s m mmit e & s m mmit lxe/ dxe is in the sbc mode of operation where a write to bit 15 of the control register is permitted. table 15. internal register utilization register number register number 8-bit mode (s m mmit xte only) register name srt sbc smt 0 0,1 control a a a 1 2,3 operational status a a a 2 4,5 current command a a a 3 6,7 interrupt mask a a a 4 8,9 pending interrupt a a a 5 a,b interrupt log list a a a 6 c,d bit word a a a 7 e,f time tag (srt and smt) miner frame timer (sbc) a a a 8 10,11 srt descriptor pointer (srt) command block pointer (sbc) a a 9 12,13 1553 status word bits a a 14,15 command block initialization count (bc) a b 16,17 initial monitor command block pointer a c 18,19 initial monitor data pointer a d 1a,1b monitor block count a e 1c,1d monitor filter a f 1e,1f monitor filter a 10 to 1f 20 to 3f illegalization a (16) total 26 10 13
s m mmit family - 84 9.1.3 dma configuration for a dma system configuration the s m mmit e & s m mmit lxe/dxe shares memory with the host and/or subsystem. the s mmm it e & s m mmit lxe/dxe gains access to memory through an arbitration process. the s mmm it e & s m mmit lxe/dxe requests access to memory by asserting the dmar signal. after receiving a grant signal (i.e., assertion of dmag ) from the bus arbiter, the s mmm it e & s m mmit lxe/dxe asserts dmack to acknowledge control of the bus. the s mmm it e & s m mmit lxe/dxe continues to assert dmack until all accesses are complete. after completion of all accesses, dmack negates releasing the bus. figure 25 shows an example dma system configuration. 9.1.4 dma transfers following the assertion of dmack , the s m mmit activates the address bus a(15:0). during write cycles, the bidirectional data bus d(15:0) activates, supplying data for the write cycle. for read cycles, the bidirectional data bus remains an input. memory control signals rcs , rrd , and rwr assert following the address bus activation. these signals control the memory chip select, output enable and write inputs. table 16 is a summary of dma activity during message processing. for both read and write memory cycles, dtack is an input to the s m mmit e & s m mmit lxe/dxe. a non-wait state memory access requires two clock cycles. for accessing slower memory devices, hold dtack to a logical one. this results in the stretching of memory cycles beyond the two clock cycles. the s m mmit e & s m mmit lxe/dxe samples dtack on the rising edge of the 24 mhz clock. if the memory logic fails to assert dtack before the rising edge of the clock, the s m mmit e & s m mmit lxe/dxe extends the memory cycle. one clock cycle is added to the memory cycle and dtack is again sampled on the clock rising edge. if dtack remains negated, the s m mmit e & s m mmit lxe/dxe continues to add one clock cycle to the memory cycle and samples dtack on each rising edge of the clock. utmc?s ut54acs220/ut54acts220 automatically generates one wait state for either the s m mmit e or s m mmit lxe/dxe. see figure 26 for additional information. see appendix 2 for additional information on the ut54acs220/ ut54acts220. assertion of dtack signals the s m mmit e & s m mmit lxe/ dxe to terminate the memory cycle. the memory cycle terminates one clock cycle after dtack assertion. for more information on memory cycles, refer to the timing diagrams and ac electrical specifications in section 20. 9.1.5 buffer mode operation the s m mmit e & s m mmit lxe/dxe have the optional use of an internal 32-word buffer to enhance message processing. use of this internal buffer decreases the number of times the s m mmit e & s m mmit lxe/dxe arbitrates for memory during message processing. the number of memory accesses required to process a command is dependent on the mode of operation (srt, sbc, smt). the s m mmit e & s m mmit lxe/dxe stores all data words associated with a receive message into memory using a single dma burst. when transmitting information, the s m mmit e & s m mmit lxe/dxe arbitrates for a memory access and extracts all data for transmission from external memory in a single dma burst. for either receive or transmit messages, the s m mmit e & s m mmit lxe/dxe does not release the memory bus until all data is transferred to or from external memory. the buffer mode of operation eliminates the s m mmit e & s m mmit lxe/ dxe arbitration for the bus each time a data word memory access is required. to enable use of the internal message buffer, the host asserts bit 6 of the control register. if the buffer feature is not enabled, the s m mmit e & s m mmit lxe/dxe arbitrates each time data storage or retrieval is required. the host or subsystem does not have access to this internal buffer.
s m mmit family - 85 figure 25. dma system configuration cpu s m mmit arbiter arbitration control signals dma memory address bus data bus memory control signals arbitration control signals
s m mmit family - 86 table 16. dma bc write scenario bc read scenario monitor write scenario rt write scenario rt read scenario note : 1. if buffer mode selected, more than 1 and up to 32 words can be read/written. number of words word type 1-32 1 data word 2 interrupt information word interrupt address word 6 control word cmd word 1 cmd word 2 data pointer status word 1 status word 2 8 control word cmd word 1 cmd word 2 data pointer status word 1 status word 2 interrupt information word interrupt address word number of words word type 1-32 1 data word 8 control word cmd word 1 cmd word 2 data pointer status word 1 status word 2 branch address timer value number of words word type 1-32 1 data word 7 control word cmd word 1 cmd word 2 data pointer status word 1 status word 2 time tag 9 control word cmd word 1 cmd word 2 data pointer status word 1 status word 2 time tag interrupt status word interrupt address word number of words word type 1-32 1 data word 3 message information word time-tag word control word 4 message information word time-tag word control word data pointer 5 message information word time-tag word control word interrupt information word interrupt address word 6 message information word time-tag word control word data pointer interrupt information word interrupt address word number of words word type 1-32 1 data word 4 control word data pointer a data pointer b broadcast data pointer
s m mmit family - 87 9.2 s m mmit xte the s m mmit xte supplies hardware designers with a flexible interface to meet the needs of state-of-the-art mil-std-1553 interfaces. the s m mmit xte contains internal sram and a memory management unit, interfaces to either 8-bit or 16-bit subsystems, supports multiplexed and non-multiplexed interfaces, and has user selectable control signals. 9.2.1 internal registers the s m mmit xte contains 32 internal registers that control and report on message activity and operation. the 32 registers are memory mapped into the subsystem memory. table 17 reviews the registers and identifies the mode of operation applicable. the host reads or writes these registers using the timing diagrams shown in figures 27 a-d. 9.2.2 memory map the s m mmit xte contains 512kbits of memory for message storage and system data storage. msel(5) determines the organization of the memory as either by 16 or by 8. when organized by 16 (i.e., msel(5) = 0) the s m mmit xte? s internal memory looks like 32k x 16 of sram. for by 8 applications (msel(5) = 1) the s m mmit xte?s internal memory looks like 64k x 8 of sram. the host reads or writes sram using the timing diagrams shown in figures 27 a-d. table 17 shows the memory organization for either 8-bit or 16-bit operation. 9.2.3 buffer mode operation for the s m mmit xte operation, disable buffer mode, i.e, control register bit 6 = logic 0. 9.2.4 hardware interface the s m mmit xte offers hardware designers a flexible interface to commonly found embedded computers. the hardware designer selects control signals, bus widths, and bus functionality (i.e., non-multiplexed versus multiplexed) to meet their interface requirements. table 18 reviews how the user selects the s m mmit xte?s operation that best meets their interface requirements. figures 28 a-d show typical system interfaces and use of the mode select inputs to configure the s m mmit xte to interface to various embedded computers. table 17. memory organization table 18. user-selectable control signals mode memory organization register location memory range 8-bit 64k x 8 0000 (hex) to 003f (hex) 0040 (hex) to ffff (hex) 16-bit 32k x 16 0000 (hex) to 001f (hex) 0020 (hex) to 7fff (hex) function input pin logic 1 logic 0 control signal select msel(2) r/ wr , cs , ds , rdy rd , wr , cs , rdy , ds bus functionality select msel(3) non-multiplexed address and data multiplexed address and data, ale interrupt select msel(4) level ( yf_int , msg_int , yf_ack , and msg_ack ) pulse ( yf_int and msg_int ) bus width select msel(5) 8-bit 16-bit
s m mmit family - 88 figure 27a. 8-bit memory and register access a(15:0) non-multiplexed memory/register read access (8-bit mode) 1,2 address address cs notes: 1. ale must be tied high. 2. latter assertion of cs , ds , rd starts cycle. 3. tie da(15:8) to v dd via a 10k resistor. 4. when using r/ wr as an input signal tie rd to a logical one. during the read cycle r/ wr remains a logical 1. 5. ds asserts to signal the s m mmit xte to place data on the bus. rd 4 da(7:0) 3 byte byte rdy ds 5 a(15:0) non-multiplexed memory register write access (8-bit mode) 1 , 2 wr or r/ wr cs rdy da(7:0) 3 address valid low byte high byte ds 4 notes: 1. ale must be tied high. 2. latter assertion of cs , ds , wr or r/ wr starts cycle. 3. tie da(15:8) to v dd via a 10k resistor. 4. ds asserts to signal that data is valid on the bus.
s m mmit family - 89 figure 27b. 16-bit memory and register access a(14:0) 3 non-multiplexed memory/register write access (16-bit mode) 1, 2 a(14:0) 3 non-multiplexed memory/register read access (16-bit mode) 1,2 address cs notes: 1. ale must be tied high. 2. latter assertion of cs , ds , rd starts cycle. 3. a15 must be tied low. 4. when using r/ wr as an input signal tie rd to a logical one. during the read cycle r/ wr remains a logic 1. 5. ds asserts to signal the s m mmit xte to place data on the bus. notes: 1. ale must be tied high. 2. latter assertion of cs , ds , wr or r/ wr starts cycle. 3. a15 must be tied low. 4. ds asserts to signal that data is valid on the bus. wr or r/ wr rd 4 cs rdy da(15:0) da(15:0) address valid word valid word rdy ds 4 ds 5
s m mmit family - 90 figure 27c. multiplexed 8-bit memory and register access da(15:0) 2,3 multiplexed memory/register read access (8-bit mode) 1 cs rd 4 ale byte byte address address rdy ds 5 da(15:0) 2,3 multiplexed memory register write access (8-bit mode) 1 notes: 1. latter assertion of cs , ds , wr or r/ wr starts cycle. 2. for multiplexed address and data interfaces ale latches the address into the s m mmit xte. data is applied to inputs da(7:0), tie a(15:0) to either a logical one or zero. 3. tie da(15:8) to v ss via a 10k resistor. 4. ds asserts to signal that data is valid on the bus. wr or r/ wr ale cs rdy low byte high byte address address ds 4 notes: 1. latter assertion of cs , ds , rd starts cycle. 2. for multiplexed address and data interfaces ale latches the address into the s m mmit xte. data is read from outputs da(7:0), tie a(15:0) to either a logical one or zero. 3. tie da(15:8) to v ss via a 10k resistor. 4. w hen using r/ wr as an input signal tie rd to a logical one. during the read cycle r/ wr remains a logic 1. 5. ds asserts to signal the s m mmit xte to place data on the bus.
s m mmit family - 91 figure 27d. multiplexed 16-bit memory and register access da(15:0) 2 multiplexed memory/register write access (16-bit mode ) 1 da(15:0) 2 multiplexed memory/register read access (16-bit mode) 1 cs notes: 1. latter assertion of cs , ds , rd starts cycle. 2. for multiplexed address and data interfaces ale latches the address into the s m mmit xte. data is read from outputs da(15:0), tie a(15:0) to either a logical one or zero. 3. ds asserts to signal the s m mmit xte to place data on the bus. notes: 1. latter assertion of cs , ds , wr or r/ wr starts cycle. 2. for multiplexed address and data interfaces ale latches the address into the s m mmit xte. data is applied to inputs da(15:0), tie a(15:0) to either a logical one or zero. 3. ds asserts to signal that data is valid on the bus. wr or r/ wr rd ale ale cs ds 3 ds 3 data address data address rdy rdy
s m mmit family - 92 figure 28a. 16-bit interface (intel type) figure 28b. 16-bit interface (motorola type) s m mmit xte transformer channel a transformer channel b cha cha chb chb da(15:0) ale rd wr msel(5) msel(2) msel(3) type cpu transformer channel a transformer channel b cha cha chb chb a(15:0) r/ wr cs cs da(7:0) to 1553 bus a to 1553 bus b to 1553 bus a to 1553 bus b s m mmit xte intel type cpu motorola ds ready rdy msel(2) msel(3) msel(5)
s m mmit family - 93 figure 28c. 8-bit interface (intel type) figure 28d. 8-bit interface (motorola type) s m mmit xte transformer channel a transformer channel b cha cha chb chb da(15:0) ale rd wr msel(5) msel(2) msel(3) type cpu transformer channel a transformer channel b cha cha chb chb a(15:0) r/ wr cs msel(5) msel(3) msel(2) cs da(7:0) to 1553 bus a to 1553 bus b to 1553 bus a to 1553 bus b s m mmit xte intel type cpu motorola ds
s m mmit family - 94 10.0 s e r i a l d a t a b u s i n t e r f a c e the s m mmit lxe/dxe & s m mmit xte manchester encoder/decoder interfaces directly to the mil-std-1553 bus via transformers, using cha- cha and chb- chb . the designer can connect the s m mmit lxe/dxe & s m mmit xte to the data bus via a short-stub (direct-coupling) connection or a long-stub (transformer-coupling) connection. use a short-stub connection when the distance from the isolation transformer to the data bus does not exceed a one-foot maximum. use a long- stub connection when the distance from the isolation transformer exceeds the one-foot maximum and is less than twenty feet. figures 29 a-c show various examples of bus coupling configurations. the s m mmit lxe/dxe & s m mmit xte is designed to function with mil-std-1553a and 1553b compatible transformers. 10.1 transmitter the transmitter section accepts manchester ii biphase ttl data and converts this data into differential phase-modulated current drive. transmitter current drivers are coupled to a mil-std- 1553 data bus via a transformer driven from the cha (chb) and cha (chb) terminals. the s m mmit lxe/dxe & s m mmit xte internally generates a signal to the transceiver for the mil-std-1553 fail-safe timer requirement. 10.2 receiver the receiver section accepts biphase differential data from a mil-std-1553 data bus at its cha (chb) and cha ( chb ) inputs. the receiver converts input data to biphase manchester ii ttl format at internal rxout and rxout terminals. the internal outputs rxout and rxout represent positive and negative excursions (respectively) of the inputs cha (chb) and cha ( chb ). 10.3 recommended thermal protection all packages should mount to or contact a heat removal rail located in the printed circuit board. to insure proper heat transfer between the package and the heat removal rail, use a thermally- conductive material between the package and the heat removal rail. use a material such as mereco xln-589 or equivalent to insure heat transfer between the package and heat removal rail. operation 55 ohms 55 ohms 1 ft max 20 ft max short-stub direct coupling long-stub transformer coupling 1.4:1 2:1 1:1.4 -15v dc z o .75 z o .75 z o z o note: z o defined per mil-std-1553b in section 4.5.1.5.2.1. figure 29a. s m mmit lxe15, xte15 bus coupling configuration cha cha
s m mmit family - 95 table 19. transformer requirements versus power supplies coupling technique -12v dc -15v dc +5v dc direct-coupled: isolation 1.2:1 1.4:1 1:2.5 transformer-coupled: isolation transformer ratio 1.66:1 2:1 1:1.79 coupling transformer ratio 1:1.4 1:1.4 1:1.4
s m mmit family - 96 20 ft max operation 55 ohms 55 ohms 1 ft max short-stub direct coupling long-stub transformer coupling 1:1.4 1.2:1 1.66:1 note: z o defined per mil-std-1553b in section 4.5.1.5.2.1. -12v dc .75 z o .75 z o z o z o figure 29b. s m mmit lxe12, xte12 bus coupling configuration 55 ohms 55 ohms 20 ft max 1:1.4 z o z o +5v dc operation 1:1.79 1:2.5 short-stub direct coupling 1 ft. max. long-stub transformer coupling .75 z o .75 z o cha cha figure 29c. s m mmit dxe, xte5 bus coupling configuration note: z o defined per mil-std-1553b in section 4.5.1.5.2.1.
97 s m mmit family 11.0 s m mmit e p i n i d e n t i f i c a t i o n a n d d e s c r i p t i o n ut69151 s m mmit e figure 30. s m mm it functional pin description memory/ processor interface jtag port status outputs clocks power & ground mode of operation remote terminal address 1553 interface subsystem fail master reset interrupts timerona timeronb ra ra rb rb ta ta tb tb cs dmar dmag dmack dtack rrd rwr rcs romen rd/ wr data (15:0 ) autoen lock rta (4:0 ) rtpty a/ b std msel (1:0) yf_int msg_int tera mrst ssysf ready trs t 24 tclk v dd gnd tck jtag address 15:0)
98 s m mmit family 11.1 s mm mit e functional pin description legend for type and active fields 1 : to = ttl output ttb = three-state ttl bidirectional ci = cmos input tui = ttl input (internally pulled high) ah = active high al = active low ti = ttl input tto = three-state ttl output pga = pingrid array fp = flatpack [ ] = 132-lead flatpack note: 1. all pins described as ttl use cmos transistors that are designed compatibility with ttl devices. 11.1.1 data bus bit number type active pin number fp pga description 15 ttb -- 4 [7] c1 bit 15 (msb) of the bidirectional data bus. 14 ttb -- 5 [8] d2 bit 14 of the bidirectional data bus. 13 ttb -- 6 [9] d1 bit 13 of the bidirectional data bus. 12 ttb -- 7 [10] f2 bit 12 of the bidirectional data bus. 11 ttb -- 8 [11] e2 bit 11 of the bidirectional data bus. 10 ttb -- 9 [15] e1 bit 10 of the bidirectional data bus. 9 ttb -- 10 [18] f1 bit 9 of the bidirectional data bus. 8 ttb -- 13 [19] g1 bit 8 of the bidirectional data bus. 7 ttb -- 14 [20] g2 bit 7 of the bidirectional data bus. 6 ttb -- 15 [24] g3 bit 6 of the bidirectional data bus. 5 ttb -- 16 [25] h1 bit 5 of the bidirectional data bus. 4 ttb -- 17 [26] h2 bit 4 of the bidirectional data bus. 3 ttb -- 18 [27] j1 bit 3 of the bidirectional data bus. 2 ttb -- 19 [30] k1 bit 2 of the bidirectional data bus. 1 ttb -- 20 [31] j2 bit 1 of the bidirectional data bus. 0 ttb -- 21 [32] l1 bit 0 (lsb) of the bidirectional data bus.
99 s m mmit family 11.1.2 address bus note: 1. address lines are inputs while dmack is inactive. 11.1.3 remote terminal address inputs bit number type radhard type non- radhard 1 active pin number fp pga description 15 tto ttb -- 64 [101] b10 bit 15 (msb) of the address bus. 14 tto ttb -- 65 [102] b9 bit 14 of the address bus. 13 tto ttb -- 66 [103] a10 bit 13 of the address bus. 12 tto ttb -- 67 [106] a9 bit 12 of the address bus. 11 tto ttb -- 68 [107] b8 bit 11 of the address bus. 10 tto ttb -- 69 [108] a8 bit 10 of the address bus. 9 tto ttb -- 70 [109] c7 bit 9 of the address bus. 8 tto ttb -- 71 [110] b7 bit 8 of the address bus. 7 tto ttb -- 72 [114] a7 bit 7 of the address bus. 6 tto ttb -- 76 [118] a5 bit 6 of the address bus. 5 tto ttb -- 77 [119] b5 bit 5 of the address bus. 4 ttb ttb -- 78 [123] a6 bit 4 of the bidirectional address bus. 3 ttb ttb -- 79 [124] a4 bit 3 of the bidirectional address bus. 2 ttb ttb -- 80 [125] b4 bit 2 of the bidirectional address bus. 1 ttb ttb -- 81 [126] a3 bit 1 of the bidirectional address bus. 0 ttb ttb -- 82 [129] a2 bit 0 (lsb) of the bidirectional address bus. name type active pin number fp pga description rta4 tui -- 37 [58] l8 remote terminal address bit 4. this is the most significant bit for the rt address. rta3 tui -- 38 [59] k8 remote terminal address bit 3. this is bit 3 of the rt address. rta2 tui -- 39 [60] l9 remote terminal address bit 2. this is bit 2 of the rt address. rta1 tui -- 40 [63] l10 remote terminal address bit 1. this is bit 1 of the rt address. rta0 tui -- 41 [64] k9 remote terminal address bit 0. this is bit 0 of the rt address. this is the least significant bit for the rt address. rtpty tui -- 42 [65] l11 remote terminal parity. this is an odd parity input for the rt address.
100 s m mmit family 11.1.4 jtag testability pins 11.1.5 biphase inputs name type active pin number fp pga description tdo tto -- 49 [79] g9 tdo. this output performs the operation of test data output as defined in the ieee standard 1149.1. this non-inverting output buffer is optimized for driving ttl loads. tck tui -- 54 [84] e9 tck. this input performs the operation of test clock input as defined in the ieee standard 1149.1. this non-inverting input buffer is optimized for driving ttl input levels. tms tui -- 51 [81] g11 tms. this input performs the operation of test mode select as defined in the ieee standard 1149.1. this non-inverting input buffer is optimized for driving ttl input levels. tdi tui -- 50 [80] g10 tdi. this input performs the operation of test data in as defined in the ieee standard 1149.1. this non- inverting input buffer is optimized for driving ttl input levels. trst tui al 48 [78] h11 trst . this input provides the reset to the tap controller as defined in the ieee standard 1149.1. this non-inverting input buffer is optimized for driving ttl input levels. when not exercising jtag, tie trst to a logical 0. name type active pin number fp pga description ra ti -- 26 [41] k4 receive channel a (true). this is the manchester- encoded true signal input for channel a. (quiescent low). ra ti -- 25 [38] l3 receive channel a (complement). this is the manchester-encoded complement signal input for channel a. (quiescent low). rb ti -- 33 [51] j5 receive channel b (true). this is the manchester- encoded true signal input for channel b. (quiescent low). rb ti -- 30 [48] l5 receive channel b (complement). this is the manchester-encoded complement signal input for channel b. (quiescent low).
101 s m mmit family 11.1.6 biphase outputs 11.1.7 dma signals note: high impedance and active low. name type active pin number fp pga description ta to -- 24 [37] l2 transmit channel a (true). this is the manchester- encoded true signal output for channel a. the signal is idle low. (quiescent low). ta to -- 23 [36] k3 transmit channel a (complement). this is the manchester-encoded complement signal output for channel a. the signal is idle low. (quiescent low). tb to -- 29 [44] k5 transmit channel b (true). this is the manchester- encoded true signal output for channel b. the signal is idle low. (quiescent low). tb to -- 28 [43] k6 transmit channel b (complement). this is the manchester-encoded complement signal output for channel b. the signal is idle low. (quiescent low). name type active pin number fp pga description dmar tto 1 al 55 [85] e11 dma request. this signal is asserted when access to ram is required. it goes inactive upon receipt of the dmag signal. dmag ti al 56 [86] e10 dma grant. once this input is received, the s mmm it is allowed to access ram. dmack tto 1 al 57 [90] f11 dma acknowledge. this signal is asserted by the s mmm it to indicate the receipt of dmag . the signal remains active until all ram bus activity is completed. dtack ti al 3 [4] b1 data transfer acknowledge. this pin indicates that a data transfer is to occur and that the s mmm it may complete the memory cycle.
102 s m mmit family 11.1.8 control signals name type active pin number fp pga description rd/ wr ti -- 63 [98] a11 read/write. this indicates the direction of data flow with respect to the host. a logic high signal means the host is trying to read data from the s mmm it, and a logic low signal means the host is trying to write data to the s mmm it. cs ti al 62 [97] c10 chip select. this pin selects the s mmm it when accessing the internal registers. rrd tto al 84 [131] a1 ram read. this signal is generated by the s mmm it to read data from ram. rwr tto al 83 [130] b3 ram write. this signal is generated by the s mmm it to write data to ram. rcs tto al 1 [2] b2 ram chip select. this signal is used in conjunction with the rrd / rwr signals to access ram. autoen tui al 60 [93] c11 auto enable. this pin, when active, enables automatic initialization. romen tto 1 al 61 [96] b11 rom enable. this pin, when active, enables the rom for automatic initialization applications. ssysf tui al 36 [57] j7 subsystem fail. upon receipt, this signal propagates directly to the rt 1553 status word. 24 mhz ci -- 75 [117] c5 24 mhz clock. the 24mhz input clock requires a 50% + 5% duty cycle with an accuracy of + 0.01%. see appendix a on ut54acts220 clock generator. mrst tui al 47 [75] h10 master reset. this input pin resets the internal encoders, decoders, all registers, and associated logic. msel(1) ti -- 45 [73] k11 mode select 1. this pin is the most significant bit for the mode select. for proper mode selection, see below: msel(1) msel(0) mode of operation 0 0 bus controller = sbc 0 1 remote terminal = srt 1 0 monitor terminal =smt 1 1 smt/srt msel(0) ti -- 46 [74] j11 mode select 0. this pin is the least significant bit for the mode select. (see msel1 for proper logic states.)
103 s m mmit family 11.1.8 control signals (continued) note: high impedance and active low. 11.1.9 status signals note: high impedance and active low. name type active pin number fp pga description tclk ti -- 2 [3] c2 timer clock. the internal timer is a 16-bit counter with a 64 m s resolution when using the 24mhz input clock. for different applications, the user may input a clock (0-6mhz) to establish the timer resolution. (duty cycle = 50% + 10%). a/ b std tui -- 44 [69] j10 military standard a or b. this pin defines whether the s mmm it will be used in a mil-std-1553a or 1553b mode of operation. lock tui al 43 [68] k10 lock. this pin, when set active, prevents software changes to both the rt address, a/ b std, and mode select. name type active pin number fp pga description teract to al 34 [52] l7 terminal active. this output pin indicates that the terminal is actively processing a 1553 command. timer ona to al 22 [35] k2 timer on a. this is a 800 m s fail-safe transmitter enable timer for channel a. this output is reset on receipt of a new command or after 760 m s. timer onb to al 27 [42] l4 timer on b. this is a 800 m s fail-safe transmitter enable timer for channel b. this output is reset on receipt of a new command or after 760ms. msg_int tto 1 al 58 [91] d11 message interrupt. this pin is active for three clock cycles (i.e., 125ns pulse) upon the occurrence of interrupt events which are enabled. yf_int tto 1 al 59 [92] d10 you failed interrupt. this pin is active for three clock cycles (i.e., 125ns pulse) upon the occurrence of interrupt events which are enabled. ready to al 35 [53] k7 ready. this signal indicates the s mmm it has completed a reset, an auto-initialization, or a bit. after assertion of the ready signal initialization of the s mmm it for operation can begin.
104 s m mmit family 11.1.10 power/ground the following shows the package location of all power and ground pins associated with the s mmm it. pin number pin number fp pga description v dd 12, 32, 53, 73 [17], [34], [50], [66], [83], [100], [115], [132] e3, l6, f9, c6 +5 volt power ( + 10%) v ss 11, 31, 52, 74 [1], [16], [33], [49], [67], [82], [99], [116] f3, j6, f10, b6 digital ground
s m mmit family - 105 12.0 s m mmit lxe/dxe p i n i d e n t i f i c a t i o n a n d d e s c r i p t i o n terac autoen lock cs dmar dmag dmack dtack rrd rwr rcs romen mrst ssysf ready rta (4:0 ) rtpty rd/ wr a/ b std msel (1:0) trs data (15:0 ) 24 tclk v ss v dd ut69151 lxe/dxe figure 31. s m mm it lxe/dxe functional pin description v ee (lx gnd memory/ processor interface jtag port status outputs clocks power & ground mode of operation remote terminal address ch ch ch ch 1553 interface tc jtag subsystem fail master reset yf_int msg_int interrupts address (15:0 )
s m mmit family - 106 12.1 s m mmit lxe/dxe pin functional description legend for type and active fields 1 : to = ttl output ttb = three-state ttl bidirectional ci = cmos input tui = ttl input (internally pulled high) ah = active high al = active low ti = ttl input tto = three-state ttl output pga = pingrid array fp = flatpack dio = differential input/output note: 1. all pins described as ttl use cmos transistors that are designed compatibility with ttl devices. 12.1.1 data bus bit number type active pin number fp pga description 15 ttb -- 97 v11 bit 15 (msb) of the bidirectional data bus. 14 ttb -- 96 v5 bit 14 of the bidirectional data bus. 13 ttb -- 95 v9 bit 13 of the bidirectional data bus. 12 ttb -- 94 u10 bit 12 of the bidirectional data bus. 11 ttb -- 93 u12 bit 11 of the bidirectional data bus. 10 ttb -- 92 v15 bit 10 of the bidirectional data bus. 9 ttb -- 91 v13 bit 9 of the bidirectional data bus. 8 ttb -- 90 v17 bit 8 of the bidirectional data bus. 7 ttb -- 89 w18 bit 7 of the bidirectional data bus. 6 ttb -- 88 w16 bit 6 of the bidirectional data bus. 5 ttb -- 87 w14 bit 5 of the bidirectional data bus. 4 ttb -- 86 w20 bit 4 of the bidirectional data bus. 3 ttb -- 85 w22 bit 3 of the bidirectional data bus. 2 ttb -- 84 v21 bit 2 of the bidirectional data bus. 1 ttb -- 83 v19 bit 1 of the bidirectional data bus. 0 ttb -- 82 v23 bit 0 (lsb) of the bidirectional data bus.
s m mmit family - 107 12.1.2 address bus note: 1. address lines are inputs while dmack is inactive. 12.1.3 remote terminal address inputs bit number type radhard type non- radhard 1 active pin number fp pga description 15 tto ttb -- 26 a2 bit 15 (msb) of the address bus. 14 tto ttb -- 25 a4 bit 14 of the address bus. 13 tto ttb -- 24 a6 bit 13 of the address bus. 12 tto ttb -- 23 c2 bit 12 of the address bus. 11 tto ttb -- 22 b3 bit 11 of the address bus. 10 tto ttb -- 21 b5 bit 10 of the address bus. 9 tto ttb -- 20 d1 bit 9 of the address bus. 8 tto ttb -- 19 c6 bit 8 of the address bus. 7 tto ttb -- 18 d3 bit 7 of the address bus. 6 tto ttb -- 17 t7 bit 6 of the address bus. 5 tto ttb -- 16 w2 bit 5 of the address bus. 4 ttb ttb -- 15 t3 bit 4 of the bidirectional address bus. 3 ttb ttb -- 14 t1 bit 3 of the bidirectional address bus. 2 ttb ttb -- 13 u6 bit 2 of the bidirectional address bus. 1 ttb ttb -- 12 u2 bit 1 of the bidirectional address bus. 0 ttb ttb -- 11 w6 bit 0 (lsb) of the bidirectional address bus. name type active pin number fp pga description rta4 tui -- 59 b17 remote terminal address bit 4. this is the most significant bit for the rt address. rta3 tui -- 58 b19 remote terminal address bit 3. this is bit 3 of the rt address. rta2 tui -- 57 a20 remote terminal address bit 2. this is bit 2 of the rt address. rta1 tui -- 56 b21 remote terminal address bit 1. this is bit 1 of the rt address. rta0 tui -- 55 a22 remote terminal address bit 0. this is bit 0 of the rt address. this is the least significant bit for the rt address. rtpty tui -- 54 b23 remote terminal parity. this is an odd parity input for the rt address.
s m mmit family - 108 12.1.4 jtag testability pins 12.1.5 biphase inputs/outputs name type active pin number fp pga description tdo tto -- 52 a18 tdo. this output performs the operation of test data output as defined in the ieee standard 1149.1. this non-inverting output buffer is optimized for driving ttl loads. tck ti -- 49 a14 tck. this input performs the operation of test clock input as defined in the ieee standard 1149.1. this non-inverting input buffer is optimized for driving ttl input levels. tms tui -- 50 c14 tms. this input performs the operation of test mode select as defined in the ieee standard 1149.1.this non-inverting input buffer is optimized for driving ttl input levels. tdi tui -- 51 a16 tdi. this input performs the operation of test data in as defined in the ieee standard 1149.1. this non- inverting input buffer is optimized for driving ttl input levels. trst tui al 53 b15 trst . this input provides the reset to the tap controller as defined in the ieee standard 1149.1. this non-inverting input buffer is optimized for driving ttl input levels.when not exercising jtag, tie trst to a logical 0. name type active pin number fp pga description cha dio -- 32 u22 channel a (true). this is the manchester-encoded true signal for channel a. cha dio -- 33 u18 channel a (complement). this is the manchester- encoded complement signal input for channel a. chb dio -- 42 c22 channel b (true). this is the manchester-encoded true signal for channel b. chb dio -- 43 c18 channel b (complement). this is the manchester- encoded complement signal for channel b.
s m mmit family - 109 12.1.6 dma signals note: 1. open drain outputs; high impedance and active low. name type active pin number fp pga description dmar tto 1 al 3 d13 dma request. this signal is asserted when access to ram is required. it goes inactive upon receipt of the dmag signal. dmag ti al 2 c10 dma grant. once this input is received, the s mmm it lx/dx is allowed to access ram. dmack tto 1 al 1 b7 dma acknowledge. this signal is asserted by the s mmm it lx/dx to indicate the receipt of dmag . the signal remains active until all ram bus activity is completed. dtack ti al 4 v7 data transfer acknowledge. this pin indicates that a data transfer is to occur and that the s mmm it lx/ dx may complete the memory cycle.
s m mmit family - 110 12.1.7 control signals name type active pin number fp pga description rd/ wr ti -- 81 b11 read/write. this indicates the direction of data flow with respect to the host. a logic high signal means the host is trying to read data from the s mmm it lx/ dx, and a logic low signal means the host is trying to write data to the s mmm it lx/dx. cs ti al 80 a10 chip select. this pin selects the s mmm it lx/dx when accessing the internal registers. rrd tto al 6 v3 ram read. this signal is generated by the s mmm it lx/dx to read data from ram. rwr tto al 7 w4 ram write. this signal is generated by the s mmm it lx/dx to write data to ram. rcs tto al 8 w12 ram chip select. this signal is used in conjunction with the rrd / rwr signals to access ram. autoen ti al 79 b9 auto enable. this pin, when active, enables automatic initialization. romen tto 1 al 78 a8 rom enable. this pin, when active, enables the rom for automatic initialization applications. ssysf ti al 75 u14 subsystem fail. upon receipt, this signal propagates directly to the rt 1553 status word. 24 mhz ci -- 74 t9 24 mhz clock. the 24mhz input clock requires a 50% + 5% duty cycle with an accuracy of + 0.01%. see appendix 2 on ut54acts220 clock generator. mrst tui al 73 d15 master reset. this input pin resets the internal encoders, decoders, all registers, and associated logic. msel(1) ti -- 72 b13 mode select 1. this pin is the most significant bit for the mode select. for proper mode selection, see below: msel(1) msel(0 ) mode of operation 0 0 bus controller = sbc 0 1 remote terminal = srt 1 0 monitor terminal = smt 1 1 smt/srt msel(0) ti -- 71 a12 mode select 0. this pin is the least significant bit for the mode select. (see msel1 for proper logic states.)
s m mmit family - 111 note: 1. open drain outputs; high impedance and active low. 12.1.8 status signals note: 1. open drain outputs; high impedance and active low. name type active pin number fp pga description tclk ti -- 68 w8 timer clock. the internal timer is a 16-bit counter with a 64 m s resolution when using the 24mhz input clock. for different applications, the user may input a clock (0-6mhz) to establish the timer resolution. (duty cycle = 50% + 10%). a/ b std tui -- 70 c16 military standard a or b. this pin defines whether the s mmm it lx/dx will be used in a mil-std- 1553a or 1553b mode of operation. lock tui al 69 t13 lock. this pin, when set active, prevents software changes to both the rt address, a/ b std, and mode select. name type active pin number fp pga description teract to al 63 u16 terminal active. this output pin indicates that the terminal is actively processing a 1553 command. msg_int tto 1 al 65 d9 message interrupt. this pin is active for three clock cycles (i.e., 125ns pulse) upon the occurrence of interrupt events which are enabled. yf_int tto 1 al 66 c12 you failed interrupt. this pin is active for three clock cycles (i.e., 125ns pulse) upon the occurrence of interrupt events which are enabled. ready to al 64 t15 ready. this signal indicates the s mmm it has completed a reset, an auto-initialization, or a bit. after assertion of the ready signal initialization of the s mmm it for operation can begin.
s m mmit family - 112 12.1.9 power/ground the following shows the package location of all power and ground pins associated with the s m mmit lxe\dxe. pin number pin number fp pga description v dd 9, 60, 62, 76, 99, 100 c4, u4, b1, d7, t5, w10 +5 volt logic power ( + 10%) v cc 30, 35, 36, 39, 40, 45 d19, t19, c24, u24 lx: +5 volt transceiver power (+10%, -5%) recommended de-coupling capacitors: 4.7 m f and .1 m f dx: +5 volt transceiver power ( + 10%) recommended de-coupling capacitors; 4.7 m f and .1 m f v ee 27, 28, 47, 48 t21, t23, d21, d23 (lx only) -12 or -15 volt transceiver power ( + 5%) recommended de-coupling capacitors: 4.7 m f and .1 m f v ss 5, 10, 61, 67, 77, 98 c8, u8, d5, d11, t11, v1 digital ground gnd 29, 31, 34, 37, 38, 41, 44, 46 t17, u20, w24, d17, c20, a24 transceiver ground
121 s m mmit family 1 2 3 4 5 6 7 8 9 1011121314151617181920 515 51 reserved remote terminal address sync status word data word sync sync data p p remote terminal address t/r subaddress/ mode data word count/mode code bit times note: t/r - transmit/receive p - parity command word message error instrumentation service request broadcast command received busy subsystem flag dynamic bus control acceptance terminal flag parity figure 33. mil-std-1553b word formats
s m mmit family - 113 13.0 s m mmit xte p i n i d e n t i f i c a t i o n a n d d e s c r i p t i o n figure 32. s m mmit xte functional pin diagram a(15:0) da(15:0) ale rd r/ wr or wr cs ds rdy ea(12:0) ed(7:0) ecs ec(2:0) yf_int msg_int yf_ack msg_ack msel(5:0) a/ b std autoen lock rta(4:0) rtpty cha cha chb chb trst tck jtags(2:0) teract ready bist ssysf 24mhz tclk mrst v dd v ss gnd v cc v ee (xt15, xt12) processor interface auto- initialization bus interrupts mode of operation remote terminal address 1553 interface jtag port status outputs subsystem fail clocks master reset power & ground ut69151 s m mmit xte
s m mmit family - 114 13.1 s m mmit xte functional pin description legend for type and active fields 1 : to = ttl output ttb = three-state ttl bidirectional ci = cmos input tui = ttl input (internally pulled high) ah = active high al = active low ti = ttl input tto = three-state ttl output pga = pingrid array fp = flatpack dio = differential input/output note: 1. all pins described as ttl use cmos transistors that are designed compatibility with ttl devices. 13.1.1 data bus da (15:0) bit number type active pin number fp pga description 15 ttb -- 17 n11 bit 15 (msb) of the bidirectional data bus. 14 ttb -- 18 l10 bit 14 of the bidirectional data bus. 13 ttb -- 19 m11 bit 13 of the bidirectional data bus. 12 ttb -- 20 l11 bit 12 of the bidirectional data bus. 11 ttb -- 21 n12 bit 11 of the bidirectional data bus. 10 ttb -- 22 m12 bit 10 of the bidirectional data bus. 9 ttb -- 23 l12 bit 9 of the bidirectional data bus. 8 ttb -- 24 l13 bit 8 of the bidirectional data bus. 7 ttb -- 25 m13 bit 7 of the bidirectional data bus. 6 ttb -- 26 l14 bit 6 of the bidirectional data bus. 5 ttb -- 28 k11 bit 5 of the bidirectional data bus. 4 ttb -- 29 k13 bit 4 of the bidirectional data bus. 3 ttb -- 30 k12 bit 3 of the bidirectional data bus. 2 ttb -- 31 j11 bit 2 of the bidirectional data bus. 1 ttb -- 32 j12 bit 1 of the bidirectional data bus. 0 ttb -- 33 j13 bit 0 (lsb) of the bidirectional data bus.
s m mmit family - 115 13.1.2 address bus a(15:0) 13.1.3 auto-initialization address bus ea(12:0) bit number type active pin number fp pga description 15 ti -- 38 j14 bit 15 (msb) of the address bus. 14 ti -- 39 h11 bit 14 of the address bus. 13 ti -- 40 h12 bit 13 of the address bus. 12 ti -- 41 h13 bit 12 of the address bus. 11 ti -- 42 g11 bit 11 of the address bus. 10 ti -- 43 g12 bit 10 of the address bus. 9 ti -- 45 g13 bit 9 of the address bus. 8 ti -- 46 g14 bit 8 of the address bus. 7 ti -- 47 f11 bit 7 of the address bus. 6 ti -- 48 f12 bit 6 of the address bus. 5 ti -- 49 f13 bit 5 of the address bus. 4 ti -- 50 d13 bit 4 of the address bus. 3 ti -- 51 e13 bit 3 of the address bus. 2 ti -- 52 c13 bit 2 of the address bus. 1 ti -- 54 e14 bit 1 of the address bus. 0 ti -- 55 c14 bit 0 (lsb) of the address bus. bit number type active pin number fp pga description 12 to -- 85 f9 bit 12 (msb) of the auto-init address bus. 11 to -- 84 f10 bit 11 of the auto-init address bus. 10 to -- 83 g10 bit 10 of the auto-init address bus. 9 to -- 82 c11 bit 9 of the auto-init address bus. 8 to -- 81 g9 bit 8 of the auto-init address bus. 7 to -- 80 e11 bit 7 of the auto-init address bus. 6 to -- 79 e10 bit 6 of the auto-init address bus. 5 to -- 78 e9 bit 5 of the auto-init address bus. 4 to -- 77 g8 bit 4 of the auto-init address bus. 3 to -- 76 h8 bit 3 of the auto-init address bus. 2 to -- 75 j7 bit 2 of the auto-init address bus. 1 to -- 74 j9 bit 1 of the auto-init address bus. 0 to -- 73 j10 bit 0 (lsb) of the auto-init address bus.
s m mmit family - 116 13.1.4 auto-initialization data bus ed(7:0) 13.1.5 remote terminal address inputs bit number type active pin number fp pga description 7 tui -- 68 k10 bit 7 (msb) of the auto-init data. 6 tui -- 67 m7 bit 6 of the auto-init data. 5 tui -- 66 n3 bit 5 of the auto-init data. 4 tui -- 65 n8 bit 4 of the auto-init data. 3 tui -- 64 m8 bit 3 of the auto-init data. 2 tui -- 63 l8 bit 2 of the auto-init data. 1 tui -- 62 n9 bit 1 of the auto-init data. 0 tui -- 61 m9 bit 0 (lsb) of the auto-init data. name type active pin number fp pga description rta4 tui -- 115 e2 remote terminal address 4. this is the most significant bit for the rt address. rta3 tui -- 116 g3 remote terminal address 3. this is bit 3 of the rt address. rta2 tui -- 117 f3 remote terminal address 2. this is bit 2 of the rt address. rta1 tui -- 118 g2 remote terminal address 1. this is bit 1 of the rt address. rta0 tui -- 119 f2 remote terminal address 0. this input is the least significant bit of the rt address. rtpty tui -- 120 g1 remote terminal parity. this is an odd parity input for the rt address.
s m mmit family - 117 13.1.6 jtag testability pins 13.1.7 biphase inputs/outputs name type active pin number fp pga description nc -- -- 59 n10 formerly mmu tdom; now no connect. v ss -- -- 58 l9 formerly mmu tdim; now tied to v ss . v ss -- -- 57 m10 formerly mmu tmsm; now tied to v ss . tdo tto -- 134 k3 s m mmit tdo. this input performs the operation of test data output as defined in ieee standard 1149.1. tdi tui -- 135 k2 s m mmit tdi. this input performs the operation of test data input as defined in ieee standard 1149.1. tms tui -- 136 j2 s m mmit tms. this input performs the operation of test mode select as defined in ieee standard 1149.1. tck ti -- 137 l2 tck. this input performs the operation of test clock as defined in ieee standard 1149.1. trst tui al 133 l3 trst . this input provides the reset to the tap controller as defined in the ieee standard 1149.1. this non-inverting input buffer is optimized for driving ttl input levels. when not exercising jtag , tie trst to a logical 0. name type active pin number fp pga description cha dio -- 92 b7 channel a (true). this is the manchester-encoded true signal for channel a. cha dio -- 93 a7 channel a (complement). this is the manchester- encoded complement signal for channel a. chb dio -- 102 a3 channel b (true). this is the manchester-encoded true signal for channel b. chb dio -- 103 a2 channel b (complement). this is the manchester- encoded complement signal for channel b.
s m mmit family - 118 13.1.8 control signals name type active pin number description fp pga cs ti al 14 a10 chip select. this pin selects the s m mmit xte?s internal memory and registers. ds ti al 12 a12 data strobe. during a write cycle, assert ds to indicate that data is valid on the data bus. during a read cycle assert ds to signal the s m mmit xte to drive the data bus. rd ti al 10 k8 read strobe. during a read cycle, assert rd to signal the s m mmit xte to drive the data bus. r/ wr or wr ti -- 11 k7 read/write or write strobe. during a write cycle assert wr to signal the s m mmit xte that data is valid on the data bus. r/ wr indicates the direction of data flow with respect to the s m mmit xte. r/ wr high indicates the s m mmit xte will drive the data bus. r/ wr low indicates an outside source will drive the data bus. msel(5) tui -- 124 d12 mode select 5. a logical zero enables the s m mmit xte?s 16-bit interface. a logical one enables the 8- bit interface. latched on the rising edge of mrst . msel(4) tui -- 125 b13 mode select 4. a logical zero enables a pulsed interrupt output. a logical one enables a level interrupt output. latched on the rising edge of mrst . msel(3) tui -- 126 c12 mode select 3. a logical zero enables the s m mmit xte?s multiplexed address and data bus interface. a logical one enables the non-multiplexed interface. latched on the rising edge of mrst . msel(2) tui -- 127 a11 mode select 2. a logical zero selects control signals rd , wr , cs , ds , and rdy . a logical one selects control signals r/ wr , cs , ds , and rdy . latched on the rising edge of mrst . msel(1) ti -- 128 j3 mode select 1. this pin in conjunction with msel(0) selects the s m mmit xte?s mode of operation. latched on the rising edge of mrst . msel(1) msel(0) mode of operation 0 0 bus controller 0 1 remote terminal 1 1 remote terminal & monitor msel(0) ti -- 129 j1 mode select 0. this pin in conjunction with msel(1) selects the s m mmit xte?s mode of operation. ec(2) tui -- 97 b10 latched on the rising edge of mrst this input sizes the auto-initialization cycle. ec(1) tui -- 98 d11 latched on the rising edge of mrst this input sizes the auto-initialization cycle.
s m mmit family - 119 ec(0) tui -- 99 b12 latched on the rising edge of mrst this input sizes the auto-initialization cycle. 24 mhz ci -- 7 n7 24 mhz clock. the 24mhz input clock requires a 50% + 5% duty cycle with an accuracy of + 0.01%. mrst tui al 130 j8 master reset. this input pin resets the internal encoder, decoder, all registers, and associated logic. ale ti ah 13 e12 address latch enable. the falling edge of this strobe latches address information into the s m mmit xte when operating with a multiplexed address and data bus. tclk ti -- 138 l7 timer clock. the internal timer is a 16-bit counter with a 64 m s resolution when using the 24mhz input clock. for applications requiring a different resolution, the user may input a clock from 0 to 6mhz to establish the timer resolution. (duty cycle equals 50% + 10%). a/ b std tui -- 122 h2 a/ b . military standard a or b. this pin defines whether the s m mmit xte operates per mil-std-1553a or mil-std-1553b. input is latched on the rising edge of mrst . lock tui al 121 h3 lock. a logical zero applied to this pin prevents software from changing the rt address, a/ b std, or mode of operation. input is latched on the rising edge of mrst . autoen tui al 131 m2 auto enable. when active this pin enables the s m mmit xte?s auto-initialization function. input is latched on the rising edge of mrst . yf_ack tui al 3 h9 you failed interrupt acknowledge. assertion of this input resets interrupt output yf_int when operating in the level mode. msg_ack tui al 5 k9 message interrupt acknowledge. assertion of this input resets interrupt output msg_int when operating in the level mode. ssysf tui al 113 d1 subsystem fail. upon assertion, this signal propagates directly to the rt?s 1553 status word. name type active pin number description fp pga
s m mmit family - 120 13.1.9 status signals 13.1.10 power/ground the following shows the package location of all power and ground pins associated with the s m mmit xte. note: 1. the v ee pins are not connected in the 5-volt only s m mmit xte. name type active pin number fp pga description yf_int tto 1 al 4 m3 you failed interrupt. this pin asserts upon the occurrence of interrupt events which are not masked. either a level output or pulse output. msg_int tto 1 al 6 l1 message interrupt. this pin asserts upon the occurrence of interrupt events which are not masked. either a level output or pulse output. ready to al 110 d9 ready . assertion of this output indicates the s m mmit xte has completed initialization or bit, and regular operation may begin. ecs to al 96 b11 chip select. auto-initialization device select. rdy tto 1 al 15 h10 access ready. assertion of this output indicates that the host can complete the s m mmit xte access. teract to al 111 f7 teract . this output indicates that the terminal is actively processing a 1553 command. bist to al 1 1. note: 1. open drain outputs; high impedance and active low. 114 d10 built-in test. assertion of this output indicates the s m mmit xte is performing an internal memory test. pin number pin number fp pga description v dd 2, 9, 16, 34, 37, 44, 60, 69, 72, 139 a8, b3, b14, f1, f14, g7, k1, k14, n2, n13 +5 volt logic power ( + 10%) v cc cha: 87, 94 chb: 101, 107 cha: c9, c10, e8 chb: c1, d3, f8 xt15 & xt12: +5 volt transceiver power (+10%,-5%) recommended de-coupling capacitors: 47 m f (tantalum), .1 m f (ceramic) and .01 m f (ceramic) xt5: +5 volt transceiver power ( + 10%) recommended de-coupling capacitors: 47 m f (tantalum), .1 m f (ceramic) and .01 m f (ceramic) v ee 1 cha: 86, 91 chb: 100, 104 cha: d7, d8 chb: c2, d2 xt15 & xt12: -12 or -15 volt transceiver power ( + 5%) v ss 1, 27, 35, 36, 53, 70, 71, 123, 132, 140 a9, a13, b2, b8, d14, h1, h7, h14, m1, m14 digital ground gnd cha: 88, 89, 90, 95 chb: 105, 106, 108, 112 cha: b9, c7, c8, e7 chb: b1, c3, e1, e3 transceiver ground
s m mmit family - 121 13.1.11 no connects pin number pin number fp pga description nc 8, 56, 59, 109 n10 no connects 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 5 1 5 5 1 reserved remote terminal address sync status word data word sync sync data p p remote terminal address t/r subaddress/ mode data word count/mode code bit times note: t/r - transmit/receive p - parity command word m e s s a g e e r r o r i n s t r u m e n t a t i o n s e r v i c e r e q u e s t b r o a d c a s t c o m m a n d r e c e i v e d b u s y s u b s y s t e m f l a g d y n a m i c b u s c o n t r o l a c c e p t a n c e t e r m i n a l f l a g p a r i t y figure 33. mil-std-1553b word formats
s m mmit family - 122 14.0 s m mmit e a b s o l u t e m a x i m u m r a t i n g s 1 (referenced to v ss ) note: 1. stresses outside the listed absolute maximum ratings may cause permanent damage to the device. this is a stress rating only, and functional operation of the device at these or any other conditions beyond limits indicated in the operational sections of this specif ication is not recommended. exposure to absolute maximum rating conditions for extended periods may affect device reliability. 15.0 s m mmit e r e c o m m e n d e d o p e r a t i n g c o n d i t i o n s symbol parameter limit unit v dd dc supply voltage -0.3 to 7.0 v v i/o voltage on any pin -.3 to v dd +.3 v t stg storage temperature -65 to +150 c t j maximum junction temperature +1 50 c i i dc input current + 10 ma t s lead temperature (soldering, 5 seconds) +300 c q jc thermal resistance, junction-to-case 7 c/w p d maximum power dissipation 2 5 w symbol parameter limit unit v dd dc supply voltage 4.5 to 5.5 v t c temperature range -55 to +125 c v in dc input voltage 0 to v dd v f in operating frequency 24 + .01% mhz d c duty cycle 50 + 5 %
s m mmit family - 123 16.0 s m mmit e dc e l e c t r i c a l c h a r a c t e r i s t i c s (v dd = 5.0v + 10%; v ss = 0v 1 ; -55 c < t c < +125 c) notes: 1. maximum allowable relative shift = 50mv. 2. 24mhz input only. 3. supplied as a design limit but not guaranteed or tested. 4. not more than one output may be shorted at a time for maximum duration of one second. 5. capacitance measured for initial qualification or design changes which may affect the value. 6. all inputs tied to v dd . symbol parameter condition min max unit v il1 low-level input voltage .8 v v il2 low-level input voltage tck input only .7 v v ih high-level input voltage 2.2 v v ilc low-level input voltage 2 .3v dd v v ihc high-level input voltage 2 .7v dd v i in input leakage current ttl driven inputs inputs with pull-up resistors inputs with pull-up resistors v in = v dd or v ss v in = v dd v in = v ss -10 -10 - 167 10 10 - 27 m a v ol low-level output voltage ttl output loads single-drive buffer cmos output loads i ol = 4.0ma i ol = 1.0 m a 7 .4 0.05 v v oh high-level output voltage ttl output loads single-drive buffer cmos output loads i oh = 4.0ma i oh = 1.0 m a 7 2.4 v dd -0.05 v i oz three-state output leakage current ttl output loads single-drive buffer v o = v dd or v ss -10 +10 m a i os short-circuit output current 3,4 ttl output loads single-drive buffer v dd = 5.5v, v o = 0v v dd = 5.5v, v o = v dd -100 +100 ma c in input capacitance 5 | = 1mhz @ 0v 15 pf c out output capacitance 5 single-drive buffer | = 1mhz @ 0v 15 pf c io bidirectional capacitance 5 | = 1mhz @ 0v 25 pf q idd quiescent current 6 | = 0mhz - non-radhard, radhard 100k radhard 300k | = 0mhz (t c = 25 o c) 1 5 35 ma m a m a s idd standby operating current | = 24mhz 40 ma
s m mmit family - 124 7. guaranteed by design, not tested.
s m mmit family - 124 17.0 s m mmit lxe/dxe & s m mmit xte a b s o l u t e m a x i m u m r a t i n g s 1 (referenced to v ss ) note: 1. stress outside the listed absolute maximum rating may cause permanent damage to the device. this is a stress rating only, and fu nctional operation of the device at these or any other conditions beyond limits indicated in the operational sections of this specification is not rec ommended. exposure to absolute maximum rating conditions for extended periods may affect device reliability. 2. mounting per mil-std-883, method 1012. symbol parameter limit unit v dd logic supply voltage -0.3 to 7.0 v p d maximum power dissipation 5 w v ee transceiver supply voltage lxe, xte15 & xte12 -22 v v cc transceiver supply voltage dxe, xte5 -0.3 to 7.0 v v dr input voltage range (receiver) lxe, xte15 & xte12 dxe, xte5 42 10 v p, l-l v p, l-l v i/o logic voltage on any pin -.3 to v dd +.3 v i i logic input current 10 ma i o peak output current (transmitter) lxe, xte15 & xte12 dxe, xte5 190 1000 ma ma t stg storage temperature -65 to +150 c t j maximum junction temperature lxe, xte15 & xte12 dxe, xte5 +150 +150 c t s lead temperature (soldering, 5 seconds) +300 c t c operating temperature case -55 to + 125 c q jc thermal resistance, junction-to-case 2 7 c/w
s m mmit family - 125 18.0 s m mmit lxe/dxe & s m mmit xte r e c o m m e n d e d o p e r a t i n g c o n d i t i o n s symbol parameter limit unit v cc transceiver supply voltage range lxe, xte15 & xte12 dxe, xte5 4.75 to 5. 5 4.5 to 5.5 v v dd logic supply voltage 4.5 to 5.5 v v ee transceiver supply voltage range lxe, xte15 & xte12 -12 or -15 ( 5%) v v dr receiver differential voltage lxe, xte15 & xte12 dxe, xte5 40 8.0 v p-p v in logic dc input voltage 0 to v dd v v ic receiver common mode input voltage range lxe, xte15 & xte12 dxe, xte5 10 5.0 v i o driver peak output current lxe, xte15 & xte12 dxe, xte5 180 700 ma s d serial data rate 0 to 1 mhz d c clock duty cycle 50 5 % t c case operating temperature range -55 to + 125 c f in operating frequency 24 .01% mhz
s m mmit family - 126 19.0 s m mmit lxe/dxe & s m mmit xte dc e l e c t r i c a l c h a r a c t e r i s t i c s 19.1 s m mmit dxe & xte dc electrical characteristics v dd = 5.0v 10% v cc = 5.0v + 10% (dxe, xte5), 5.0v +10%, -5% (lxe, xte15 & xte12) v ee = -12.0v or -15.0v 5% (lxe, xte15 & xte12) v ss = 0v 1 gnd = 0v 1 -55 c < t c < +125 c notes: 1. maximum allowable relative shift = 50mv. 2. cmos input only. 3. supplied as a design limit but not guaranteed or tested. 4. not more than one output may be shorted at a time for maximum duration of one second. 5. capacitance measured for initial qualification or design changes which may affect the value. 6. for all pins except cha, cha , chb, and chb . symbol parameter condition minimum maximum unit v il1 low-level input voltage .8 v v il2 low-level input voltage tck input only .7 v v ih high-level input voltage 2.2 v v ilc low-level input voltage 2 .3v dd v v ihc high-level input voltage 2 .7v dd v i in input leakage current ttl driven inputs inputs with pull-up resistors inputs with pull-up resistors v in = v dd or v ss v in = v dd v in = v ss -10 -10 -167 +10 +10 -27 m a v ol low-level output voltage ttl output loads single-drive buffer cmos output loads i ol = 4.0ma i ol = 1.0 m a 3 .4 0.05 v v oh high-level output voltage ttl output loads single-drive buffer cmos output loads i oh = 4.0ma i oh = 1.0 m a 3 2.4 v dd -0.05 v i oz three-state output leakage current ttl output loads single-drive buffer v o = v dd or v ss -10 +10 m a i os short-circuit output current 3,4 ttl output loads single-drive buffer v dd = 5.5v, v o = 0v v dd = 5.5v, v o = v dd -100 +100 ma c in input capacitance 5 | = 1mhz @ 0v 45 pf c out output capacitance 5 single-drive buffer | = 1mhz @ 0v 45 pf c io bidirectional capacitance 5,6 | = 1mhz @ 0v 45 pf
s m mmit family - 127 19.2 s m mmit lxe & xte (15 & 12) dc electrical characteristics 1,2 v dd = 5.0v 10% v cc = 5.0v +10%, -5% v ee = -12.0v or -15.0v 5% v ss = 0v 1 gnd = 0v 1 -55 c < t c < +125 c notes: 1. maximum allowable relative shift = 50mv. 2. as specified in test conditions. 3. all inputs tied to v dd . 4. guaranteed by characterization, not tested. 19.3 s m mmit dxe & xte (5) dc electrical characteristics 1,2 v dd = 5.0v 10% v cc = 5.0v + 10% v ss = 0v 1 gnd = 0v 1 -55 c < t c < +125 c notes: 1. maximum allowable relative shift = 50mv. 2. all inputs tied to v dd . 3. guaranteed by characterization, not tested. symbol parameter condition minimum maximum unit i cc v cc supply current v ee = -12v v cc = 5v 0% duty cycle (non-transmitting) 50% duty cycle (? = 1mhz) 4 100% duty cycle (? = 1mhz) 4 v ee = -15v v cc = 5v 0% duty cycle (non-transmitting) 50% duty cycle (? = 1mhz) 4 100% duty cycle (? = 1mhz) 4 140 140 140 140 140 140 ma ma ma ma ma ma i ee i ee supply current v ee = -12v v cc = 5v 0% duty cycle (non-transmitting) 50% duty cycle (? = 1mhz) 4 100% duty cycle (? = 1mhz) v ee = -15v v cc = 5v 0% duty cycle (non-transmitting) 50% duty cycle (? = 1mhz) 4 100% duty cycle (? = 1mhz) 80 180 270 80 180 270 ma ma ma ma ma ma q idd quiescent current 3 | = 0mhz xt | = 0mhz lx 15 1 ma ma q idd quiescent current 3 | = 0mhz lx t c = 25 o c 35 m a s idd standby operating current | = 24mhz 80 ma symbol parameter condition minimum maximum unit i cc v cc supply current 0% duty cycle (non-transmitting) 25% duty cycle (? = 1mhz) 3 50% duty cycle (? = 1mhz) 3 87.5% duty cycle (? = 1mhz) 55 250 410 650 ma ma ma ma q idd quiescent current 2 | = 0mhz xt | = 0mhz dx - non-radhard, radhard 100k radhard 300k 15 1 5 ma ma m a q idd quiescent current 2 | = 0mhz dx, t c = 25 o c 35 m a s idd standby operating current | = 24mh z 4 0 m a
s m mmit family - 128 20.0 s m mmit e & s m mmit lxe/dxe ac e l e c t r i c a l c h a r a c t e r i s t i c s ( | = 24mhz .01%, duty cycle 50% 5%) notes: 1. read cycle followed by a read cycle - minimum 45ns. read cycle followed by a write cycle - minimum 45ns. write cycle followed by a read cycle - minimum 85ns. write cycle followed by a write cycle - minimum 85ns. 2. minimum pulse width from latter rising edge of rd/ wr or cs to first falling edge. 3. guaranteed by characterization (not tested). symbol parameter minimum maximum units t a address setup time 0 -- ns t b data setup time 10 -- ns t c data hold time 8 -- ns t d address hold time 8 -- ns t e cs to cs - 105 -- ns t f access delay 1,2 85 -- ns t g rd/ wr assertion to cs assertion 3 0 -- ns t h cs negation to rd/ wr negation 3 0 -- ns t i cs assertion to output enable 0 40 ns t j cs negation to output three-state 3 5 35 ns a(4:0) d(15:0) rd/ wr cs t a t b t c t d data valid address valid t f t e t i t j t h t g figure 34. register write timing
s m mmit family - 129 notes: 1. guaranteed by characterization (not tested). 2. minimum pulse width from latter rising edge of rd/ wr or cs to first falling edge. 3. read cycle followed by a read cycle - minimum 45ns. read cycle followed by a write cycle - minimum 45ns. write cycle followed by a read cycle - minimum 85ns. write cycle followed by a write cycle - minimum 85ns. figure 35. register read timing a(4:0) d(15:0) rd/ wr cs t a t b t c t d data valid address valid t e t f t g data valid symbol parameter minimum maximum units t a address setup time 0 -- ns t b cs assertion to output enable data valid -- 95 ns t c cs negation to output disabled 1 5 35 ns t d address hold time 0 -- ns t e cs assertion to output enable data invalid 0 40 ns t f access delay 2,3 45 -- ns t g cs to cs - 105 -- ns
s m mmit family - 130 notes: 1. pulse width duration is measured with respect to the s m mmit recognizing dtack assertion. 2. guaranteed by characterization (not tested). figure 36. memory write timing symbol parameter minimum maximum units t a address propagation delay - radhard - non-radhard 0 0 18 21 ns ns t b address valid to rcs , rwr assertion 15 35 ns t c dtack setup time 10 -- ns t d rcs and rwr hold time 1 20 50 ns t e data propagation delay 20 60 ns t g address hold time 10 30 ns t h dtack hold time 10 -- ns t i rwr and rcs pulse width ( dtack tied to ground) - radhard - non-radhard 34 32 -- -- ns ns t j rwr and rcs - to dmack - 2 15 125 ns t k data hold time 2 10 40 ns a(15:0) d(15:0) t e t g t a 24mhz data valid address valid t k rwr rcs dtack t b t c t h t d t i t j dmack
s m mmit family - 131 notes: 1. pulse width duration is measured with respect to the s mmm it recognizing dtack assertion. 2. guaranteed by chacterization (not tested). figure 37. memory read timing symbol parameter minimum maximum units t a address propagation delay - radhard - non-radhard 0 0 18 21 ns t b address valid to rcs , rrd assertion 15 35 ns t c dtack setup time 10 -- ns t d rcs and rrd hold time 1 20 50 ns t e data setup delay - radhard - non-radhard 1 4 10 -- -- ns ns t f data hold delay - radhard - non-radhard 0 2 -- -- ns ns t g address hold time 10 30 ns t h dtack hold time 10 -- ns t i rrd and rcs pulse width ( dtack tied to ground) - radhar d - non-radhard 34 32 -- -- ns ns t j rrd and rcs - to dmack - 2 15 45 ns a(15:0) d(15:0) rrd rcs dtack t b t c t h t d t g t a 24mhz data valid t i address valid t f t e t j dmack
s m mmit family - 132 note: 1. guaranteed by characterization (not tested). figure 38. dma timing teract t a t b dmack a(15:0) dmar dmag t c t e t f t d t g t h t j t i rrd , rwr , rcs valid symbol parameter minimum maximum units t a teract assertion to dmar assertion 5 -- m s t b dmar assertion to dmack negation bus controller remote terminal remote terminal and monitor monitor -- -- -- -- 16 7 7 7 m s m s m s m s t c dmag assertion to dmack assertion - radhard - non-radhard 0 5 30 30 ns ns t d dmag assertion to dmar negation 1 0 35 ns t e dmack assertion to address bus active - radhard - non-radhard 0 -5 5 5 ns ns t f dmack assertion to dmag negation 10 -- ns t g dmack negation to dmar assertion 500 -- ns t h dmack assertion to ram control active (negated) - radhard - non-radhard 0 -5 5 5 ns ns t i dmack negation to a(15:0) three-state 1 -- 5 ns t j dmack negation t o ram control disabled 1 -- 5 ns
s m mmit family - 133 note: 1. s m mmit must receive at least 3 24mhz clock cycles before deassertion of mrst . 2. power-up master reset timing with auto-initialization enabled. 3. power-up master reset timing with auto-initialization disabled. figure 39. power-up master reset timing symbol parameter minimum maximum units t a mrst pulse width 500 -- ns t b mrst negation to romen assertion -- 5 m s t c mrst negation to ready assertion -- 10 m s t d dmack negation to romen negation -- 500 ns mrst t a t b t d romen 2 dmack 2 autoen 2 ready 2 24mhz 1 autoen 3 ready 3 t c
s m mmit family - 134 note: 1. guaranteed by characterization (not tested). figure 40. biphase timing (s m mmit only) symbol parameter minimum maximum units t a biphase output skew -- 10 ns t b biphase input skew (low to high) 1 -- 250 ns t c biphase input skew (high to low) 1 -- 250 ns t d biphase input pulse width 1 250 -- ns ta , tb ra, rb t a ta, tb ra , rb t b t c t d
s m mmit family - 136 note: 1. a cycle begins on the latter falling edge of cs , ds and rd . 2. a cycle ends on the rising edge of either cs , ds and rd . 3. non-buffered mode of operation. 4. guaranteed by design, not tested. figure 42. non-multiplexed memory/register read (8-bit) symbol parameter minimum maximum units t as address setup time 4 5 -- ns t qx data low z 4 0 30 ns t ah address hold time 4 0 -- ns t qv data valid 4 20 -- ns t qz data high z 4 0 32 ns t rdyl rdy low time (non-contended) 245 ns t rdyl rdy low time (contended ) 4 1700 3 ns t rdyh rdy high time 4 0 25 ns t rdyx rdy low z 4 3 -- ns t rdyz rdy high -- 33 ns a(15:0) da(7:0) cs ds rd 1,2 t qv valid valid t as t qx t rdyl t rdyh t qz t ah rdy t rdyx t rdyz
s m mmit family - 137 notes: 1. a cycle begins on the latter falling edge of cs , ds and wr or r/ wr . 2. a cycle ends on the rising edge of either cs , ds and wr or r/ wr . 3. non-buffered mode of operation. 4. for applications not using rdy signal. 5. guaranteed by design, not tested. 6. guaranteed by device characterization, not tested. 7. a15 must be tied low. figure 43. non-multiplexed memory/register write (16-bit) symbol parameter minimum maximum units t as address setup time 6 5 -- ns t ds data setup time 6 -- 20 ns t wp write pulse width (non-contended) 5 230 4 -- ns t wp write pulse width (contended) 5 1700 3,4 -- ns t ah address hold time 6 0 -- ns t dh data hold time 6 0 -- ns t rdyl rdy low time (non-contended) -- 245 ns t rdyl rdy low time (contended) 5 -- 1700 3 ns t rdyh rdy high time 6 0 25 ns t rdyx rdy low z 6 3 -- ns t rdyz rdy high z -- 33 ns t cyc minimum cycle time 5 20 -- ns a(14:0) 7 da(15:0) cs ds rdy wr or r/ wr 1,2 t as t ds t wp t rdyl t dh t ah t rdyz t rdyx t rdyh valid valid t cyc
s m mmit family - 138 notes: 1. a cycle begins on the latter falling edge of cs , ds and rd . 2. a cycle ends on the rising edge of either cs , ds and rd . 3. non-buffered mode of operation. 4. guaranteed by design, not tested. 5. guaranteed by device characterization, not tested. 6. a15 must be tied low. figure 44. non-multiplexed memory/register read (16-bit) a(14:0) 6 da(15:0) cs ds rd 1,2 t qv valid valid t as t qx t rdyl t rdyh t qz t ah rdy t rdyx t rdyz symbol parameter minimum maximum units t as address setup time 5 5 -- ns t qx data low z 5 0 30 ns t ah address hold time 5 0 -- ns t qv data valid 5 20 -- ns t qz data high z 5 0 32 ns t rdyl rdy low time (non-contended) -- 245 ns t rdyl rdy low time (contended) 4 -- 1700 3 ns t rdyh rdy high time 5 0 25 ns t rdyx rdy low z 5 3 -- ns t rdyz rdy high z -- 33 ns
s m mmit family - 139 notes: 1. a cycle begins on the latter falling edge of cs , ds and wr or r/ wr . 2. a cycle ends on the rising edge of either cs , ds and wr or r/ wr . 3. non-buffered mode of operation. 4. for applications not using rdy signal. 5. guaranteed by design, not tested. 6. guaranteed by device characterization, not tested. figure 45. multiplexed memory/register write (8-bit) symbol parameter minimum maximum units t as address setup time 5 0 -- ns t ahal ale pulse width 5 20 -- ns t ds data setup time 6 -- 0 ns t wp write pulse width (non-contended) 5 230 4 -- ns t wp write pulse width (contended) 5 1700 3,4 -- ns t ah address hold time 6 5 -- ns t dh data hold time 6 0 -- ns t rdyl rdy low time (non-contended) 6 -- 245 ns t rdyl rdy low time (contended) 5 -- 1700 3 ns t rdyh rdy high time 5 0 25 ns t rdyx rdy low z 5 3 -- ns t rdyz rdy high z 5 -- 33 ns t als address latch setup time 6 5 -- ns t cyc minimum cycle time 5 20 -- ns da(15:0) ale cs ds rdy wr or r/ wr 1,2 t ah t ds t wp t dh data address t as t ahal t rdyl t rdyz t rdyh t rdyx t als t cyc
s m mmit family - 140 notes: 1. a cycle begins on the latter falling edge of cs, ds and rd . 2. a cycle ends on the rising edge of either cs , ds and rd . 3. non-buffered mode of operation. 4. guaranteed by design, not tested. figure 46. multiplexed memory/register read (8-bit) symbol parameter minimum maximum units t as address setup time 4 0 -- ns t ahal ale pulse width 4 20 -- ns t qx data low z 4 0 30 ns t ah address hold time 5 -- ns t qv data valid 12 -- ns t qz data high z 3 32 ns t rdyl rdy low time (non-contended) 4 -- 245 ns t rdyl rdy low time (contended) 4 -- 1700 3 ns t rdyh rdy high time 4 0 25 ns t rdyx rdy low z 4 3 -- ns t rdyz rdy high z 4 -- 33 ns t als address latch setup time 4 5 -- ns da(15:0) ale cs ds rdy rd 1,2 t rdyl t qz t ah address data t ahal t qx t as t rdyh t qv t rdyx t rdyz t als
s m mmit family - 141 notes: 1. a cycle begins on the latter falling edge of cs , ds and wr or r/ wr 2. a cycle ends on the rising edge of either cs , ds and wr or r/ wr . 3. non-buffered mode of operation. 4. for applications not using rdy signal. 5. guaranteed by design, not tested. figure 47. multiplexed memory/register write (16-bit) symbol parameter minimum maximum units t as address setup time 5 0 -- ns t ahal ale pulse width 5 20 -- ns t ds data setup time 5 -- 20 ns t wp write pulse width (non-contended) 5 230 4 -- ns t wp write pulse width (contended) 5 1700 3,4 -- ns t ah address hold time 5 5 -- ns t dh data hold time 5 5 -- ns t rdyl rdy low time (non-contended) 5 -- 245 ns t rdyl rdy low time (contended) 5 -- 1700 3 ns t rdyh rdy high time 5 0 25 ns t rdyx rdy low z 5 3 -- ns t rdyz rdy high z 5 -- 33 ns t als address latch setup time 5 5 -- ns t cyc minimum cycle time 5 20 -- ns da(15:0) ale cs ds rdy wr or r/ wr 1,2 t ah t ds t wp t rdyl t rdyh t dh data address t as t ahal t rdyx t rdyz t als t cyc
s m mmit family - 142 notes: 1. a cycle begins on the latter falling edge of cs , ds and rd . 2. a cycle ends on the rising edge of either cs , ds and rd 3. non-buffered mode of operation. 4. guaranteed by design, not tested. figure 48. multiplexed memory/register read (16-bit) symbol parameter minimum maximum units t as address setup time 4 0 -- ns t ahal ale pulse width 4 20 -- ns t qx data low z 4 0 30 ns t ah address hold time 4 5 -- ns t qv data valid 4 20 -- ns t qz data high z 4 3 32 ns t rdyl rdy low time (non-contended) 4 -- 245 ns t rdyl rdy low time (contended) 4 -- 1700 3 ns t rdyh rdy high time 4 0 25 ns t rdyx rdy low z 4 3 -- ns t rdyz rdy high z 4 -- 33 ns t als address latch setup time 4 5 -- ns da(15:0) ale cs ds rdy rd 1,2 t as t rdyl t rdyh t qz t ah address t ahal t qx t qv t rdyx t rdyz data t als
s m mmit family - 143 notes: 1. guaranteed by design, not tested. figure 49. auto-initialization read cycle symbol parameter minimum maximum units t as address setup time 1 35 -- ns t ah address hold time 1 35 -- ns t ds data setup time 1 41 -- ns t dh data hold time 1 5 -- ns t rp read pulse width 1 160 -- ns t s setup time 1 45 -- ns ea(12:0) ed(7:0) ecs t ds t rp t dh t ah ec(2:0) mrst t s msel(5:0) n n + 1 t dh t as valid valid
s m mmit family - 144 symbol parameter minimum maximum units t a maximum register/memory time bus controller 1 remote terminal 1 remote terminal and monitor 1 monitor 1 -- -- -- -- 16 7 7 7 m s m s m s m s address bus a(15:0), a(14:0), da(15:0), or da(14:0) control signals ( ds , cs , rd , r/ wr) address valid t a figure 50. maximum cycle time notes: 1. guaranteed by design, not tested.
145 s m mmit family 22.0 s m mmit lx/dx & s m mmit xt r e c e i v e r e l e c t r i c a l c h a r a c t e r i s t i c s 22.1 s m mmit lx & xt (15 & 12) receiver electrical characteristics v dd = 5.0v 10% v cc = 5.0v +10%, -5% v ee = -12.0v or -15.0v 5% v ss = 0v gnd = 0v -55 c < t c < +125 c notes: 1. guaranteed by device characterization, not tested. 2. pass/fail criteria per the test method described in mil-hdbk-1553 appendix a, rt validation test plan, section 5.1.2.2, common mode rejection. 3. guaranteed by design, not tested. symbol parameter condition minimum maximum unit r iz 1 differential (receiver) input impedance input | = 1mhz (no transformer in circuit) 15 kohms v ic 3 common mode input voltage direct-coupled stub; input 1.2v pp , 200ns rise/fall time 25ns, | = 1mhz -10 +10 v v th input threshold voltage (no response) 1 input threshold voltage (no response) input threshold voltage (response) 1 input threshold voltage (response) transformer-coupled stub; input at | = 1mhz, rise/fall time 200ns (receiver output 0 ? 1 transition) direct-coupled stub; input at | = 1mhz, rise/fall time 200ns (receiver output 0 ? 1 transition) transformer-coupled stub; input at | = 1mhz, rise/fall time 200ns (receiver output 0 ? 1 transition) direct-coupled stub; input at | = 1mhz, rise/fall time 200ns (receiver output 0 ? 1 transition) 0.86 1.20 0.20 0.28 14.0 20.0 1 v pp,l-l v pp,l-l v pp,l-l v pp,l-l cmrr 1 common mode rejection ratio pass/fail 2 n/a
146 s m mmit family 22.2 s m mmit dx & xt (5) receiver electrical characteristics v dd = 5.0v 10% v cc = 5.0v + 10% v ss = 0v gnd = 0v -55 c < t c < +125 c notes: 1. guaranteed by device characterization, not tested. 2. pass/fail criteria per the test method described in mil-hdbk-1553 appendix a, rt validation test plan, section 5.1.2.2, common mode rejection. 3. guaranteed by design, not tested. symbol parameter condition minimum maximum unit v ic 3 common mode input voltage direct-coupled stub; input 1.2v pp , 200ns rise/fall time 25ns, | = 1mhz -10 +10 v v th input threshold voltage (no response) 3 input threshold voltage (no response) input threshold voltage (response) 3 input threshold voltage (response) 3 transformer-coupled stub; input at | = 1mhz, rise/fall time 200ns at (receiver output 0 ? 1 transition) direct-coupled stub; input at | = 1mhz, rise/fall time 200ns at (receiver output 0 ? 1 transition) transformer-coupled stub; input at | = 1mhz, rise/fall time 200ns at (receiver output 0 ? 1 transition) direct-coupled stub; input at | = 1mhz, rise/fall time 200ns at (receiver output 0 ? 1 transition) 0.86 1.20 0.20 0.28 14.0 20.0 v pp,l-l v pp,l-l v pp,l-l v pp,l-l cmrr 1,2 common mode rejection ratio pass/fail n/a
147 s m mmit family 23.0 s m mmit lx/dx & s m mmit xt t r a n s m i t t e r e l e c t r i c a l c h a r a c t e r i s t i c s 23.1 s m mmit lx & xt (15 & 12) transmitter electrical characteristics v dd = 5.0v 10% v cc = 5.0v +10%, -5% v ee = -12.0v or -15.0v 5% v ss = 0v gnd = 0v -55 c < t c < +125 c note: 1. guaranteed by device characterization, not tested. 2. tested in accordance with the method described in mil-std-1553b output symmetry, section 4.5.2.1.1.4. 3. guaranteed by design, not tested. symbol parameter minimum maximum unit condition v o output voltage swing per mil-std-1553b 3 (see figure 52) per mil-std-1553b (see figure 52) per mil-std-1553a 3 (see figure 52) 18 6.0 6.0 27 9 20 v pp,l-l v pp,l-l v pp,l-l transformer-coupled stub, figure 51, point a; input | = 1mhz, r l = 70 ohms direct-coupled stub, figure 51, point a; input | = 1mhz, r l = 35 ohms figure 51, point a; input | = 1mhz, rl = 35 ohms v ns 1 output noise voltage differential (see figure 52) 14 5 mv-rms l- l mv-rms l- l transformer-coupled stub, figure 51, point a; input | = dc to 10mhz, rl = 70 ohms direct-coupled stub, figure 51, point a; input | = dc to 10mhz, r l = 35 ohms v os 1,2 output symmetry (see figure 52) -250 -90 +250 +90 mv pp,l-l mv pp,l-l transformer-coupled stub, figure 51, point a; rl = 70 ohms, measurement taken 2.5 m s after end of transmission direct-coupled stub, figure 51, point a; r l = 35 ohms, measurement taken 2.5 m s after end of transmission v dis 1 output voltage distortion (overshoot or ring) (see figure 52) -900 -300 +900 +300 mv peak,l-l mv peak,l-l transformer-coupled stub, figure 51, point a; r l = 70 ohms direct-coupled stub, figure 51, point a; r l = 35 ohms t iz 1 terminal input impedance 1 2 kohm kohm transformer-coupled stub, figure 51, point a; input | = 75khz to 1mhz (power on or power off; non- transmitting, r l removed from circuit). direct-coupled stub, figure 51, point a; input | = 75khz to 1mhz (power on or power off; non-transmitting, r l removed from circuit).
148 s m mmit family 23.2 s m mmit dx & xt (5) transmitter electrical characteristics v dd = 5.0v 10% v cc = 5.0v + 10% v ss = 0v gnd = 0v -55 c < t c < +125 c note: 1. guaranteed by device characterization, not tested. 2. tested in accordance with the method described in mil-std-1553b output symmetry, section 4.5.2.1.1.4. symbol parameter minimum maximum unit condition v o output voltage swing per mil-std-1553b 1 (see figure 52) per mil-std-1553b (see figure 52) per mil-std-1553a 1 (see figure 52) 18 6.0 6.0 27 9 20 v pp,l-l v pp,l-l v pp,l-l transformer-coupled stub, figure 51, point a; input | = 1mhz, r l = 70 ohms direct-coupled stub, figure 51, point a; input | = 1mhz, r l = 35 ohms v ns 1 output noise voltage differential (see figure 52) 14 5 mv-rms l- l mv-rms l- l transformer-coupled stub, figure 51, point a; input | = dc to 10mhz, rl = 70 ohms direct-coupled stub, figure 51, point a; input | = dc to 10mhz, r l = 35 ohms v os 1,2 output symmetry (see figure 52) -250 -90 +250 +90 mv pp,l-l mv pp,l-l transformer-coupled stub, figure 51, point a; r l = 70 ohms, measurement taken 2.5 m s after end of transmission direct-coupled stub, figure 51, point a; r l = 35 ohms, measurement taken 2.5 m s after end of transmission v dis 1 output voltage distortion (overshoot or ring) (see figure 52) -900 -300 +900 +300 mv peak,l-l mv peak,l-l transformer-coupled stub, figure 51, point a; r l = 70 ohms direct-coupled stub, figure 51, point a; r l = 35 ohms t iz 1 terminal input impedance 1 2 kohm kohm transformer-coupled stub, figure 51, point a; input | = 75khz to 1mhz (power on or power off; non- transmitting, r l removed from circuit). direct-coupled stub, figure 51, point a; input | = 75khz to 1mhz (power on or power off; non-transmitting, r l removed from circuit).
149 s m mmit family 24.0 s m mmit lx/dx & s m mmit xt ac e l e c t r i c a l c h a r a c t e r i s t i c s 24.1 s m mmit lx & xt (15 & 12) ac electrical characteristics v dd = 5.0v 10% v cc = 5.0v +10%, -5% v ee = -12.0v or -15.0v 5% v ss = 0v gnd = 0v -55 c < t c < +125 c 24.2 s m mmit dx & xt (5) ac electrical characteristics v dd = 5.0v 10% v cc = 5.0v + 10% v ss = 0v gnd = 0v -55 c < t c < +125 c symbol parameter minimum maximum unit condition t r, t f transmitter output rise/ fall time (see figure 53) 100 300 ns input | = 1mhz 50% duty cycle: direct-coupled rl = 35 ohms output at 10% through 90% points txout, txout . figure 53. t rzcd zero crossing distortion (see figure 54) -150 150 ns direct-coupled stub; input | = 1mhz, 3 v pp (skew input 150ns), rise/fall time 200ns. t tzcs zero crossing stability (see figure 54) -25 25 ns input txin and txin should create transmitter output zero crossings at 500ns, 1000ns, 1500ns, and 2000ns. these zero crossings should not deviate more than 25ns. symbol parameter minimum maximum unit condition t r, t f transmitter output rise/ fall time (see figure 53) 100 300 ns input | = 1mhz 50% duty cycle: direct-coupled rl = 35 ohms output at 10% through 90% points txout, txout . figure 53. t rzcd zero crossing distortion (see figure 54) -150 150 ns direct-coupled stub; input | = 1mhz, 3 v pp (skew input 150ns), rise/fall time 200ns. t tzcs zero crossing stability (see figure 54) -25 25 ns input txin and txin should create transmitter output zero crossings at 500ns, 1000ns, 1500ns, and 2000ns. these zero crossings should not deviate more than 25ns.
150 s m mmit family figure 51. transceiver test circuit mil-std-1553b a terminal notes: 1. transformer coupled stub: terminal is defined as transceiver plus isolation transformer. 2. direct coupled stub: terminal is defined as transceiver plus isolation transformer and fault resistors. rl txout txout
151 s m mmit family figure 52. transmitter output characteristics (v dis , v os , v ns , v o ) figure 53. transmitter output zero crossing stability, rise time, fall time (t tzcs , t r , t f ) figure 54. receiver input zero crossing distortion (t rzcd ) 0 volts 0 volts v dis (ring) v dis (overshoot) v o v ns v os 90% 10% 10% 90% v o t r t f t tzcs t rzcd v in
s m mmit family - 152 25.0 p a c k a g i n g notes: 1. all package finishes are per mil-prf-38535. 2. letter designations are for cross-reference to mil-std-1835. 3. numbering and lettering on the ceramic are not subject to visual or marking criteria. 4. true position applies to pins at the base plane (datum c). 5. true position applies at pin tips. 6. pin c3 is a guide pin only. 7. approximately 9.0 grams. figure 55. s m mmit e 85-pin pingrid array e 0.100 typ l k j h g f e d c b a 1 2 3 4 5 6 7 8 9 10 11 pin #1 id bottom view a-a 0.003 min. typ. d1/e1 1.000 0.070 + 0.010 dia. typ. top view standoff 0.050 dia + 0.005 pin 1 id plating tab optional -a- d 1.100 + 0.012 0.100 e 1.100 + 0.012 0.080 ref. typ. 0.040 ref. typ. vss vdd v d d q v s s q v s s q v d d q -b- side view a1 0.114 0.080 l a a -c- (base plane) q 0.050 + 0.010 b 0.018 + 0.002 5 5 - p g a 7 1 2 7 v d d v s s
s m mmit family - 153 notes: 1. all package finishes are per mil-prf-38535. 2. letter designations are for cross-reference to mil-std-1835. 3. numbering and lettering on the ceramic are not subject to visual or marking criteria. 4. approximately 8.0 grams. figure 56. s m mmit e 85-lead flatpack (50mil lead spacing) bottom view a-a top view side view detail a 0.005 min. typ. l 0.0260 min. ref. 0.000 min. c 0.007 + 0.001 0.007 + 0.001 a a 0.108 max. a1 0.088/0.072 see detail a lead kovar plating tab optional b 0.016 + 0.002 e 0.050 typ. 0.040 ref. typ. 0.040 ref. typ. vddq vssq v s s v d d v d d q v s s q v s s v d d 8 4 - f p 7 0 2 3 hd/he 1.810 + 0.015 sq. d/e 1.150 + 0.012 0.040 ref. typ. pin 1 i.d. geometry optional (counter-clockwise) a
s m mmit family - 154 notes: 1. all exposed metalized areas are gold plated over nickel plating per mil-prf-38535. 2. the lid is electrically connected to v ss . 3. lead finish is in accordance with mil-prf-38535. 4. letter designations are to cross-reference to mil-std-1835. 5. lead true position to tolerances and coplanarity are not measured. figure 57. s m mmit e 132-lead flatpack
s m mmit family - 155 -a- d 1.3100.015 index mark in this area 0.070 x 45o ref. 0.040 ref. 0.040 ref. 0.130 ref. e 1.060 0.015 -b- a a -c- base plane a 0.125 0.100 0.315 0.270 l 0.180 0.008 top view notes: 1. true position applies to pins at base plane (datum c). 2. true position applies at pin tips. 3. all package finishes are per mil-prf-38535. 4. letter designations are for cross-reference to mil-std-1835. bottom view a-a side view 0.030 m c a b 1 2 ?? 0.010 c 0.0180.002 d1 1.150 0.100 e 0.050 0.900 0.600 0.037 min.typ. d c b a w v u t die outlines shown for reference only index mark vssq vddq v s s v d d 9 6 p i n 7 1 3 7 1 2 3 4 5 6 7 8 9 10 12 14 16 18 20 22 24 (3 places) figure 58. s m mmit lxe/dxe 96-pin pingrid array m m m
s m mmit family - 156 l 0.350 min. lead length figure 59. s m mmit lxe/dxe 100-lead top view view a-a side view detail a a a see detail a e1 0.9850.015 0.200 ref. b 0.0080.002 typ. e 0.025 0.130 0.090 lead #1 index geometry optional 0.000 min. 0.0080.006 c 0.006 +0.0015 - 0.001 n.c.s. material: dark ceramic lead material: kovar l 0.525 min. lead length 0.040 ref. 51 75 100fp 2 6 5 0 1 0 0 1 2 5 notes: 1. all package finishes are per mil-prf-38535. 2. letter designations are for cross-reference to mil-std-1835. d1 1.3500.015 d/e 2.580 max. sq.
s m mmit family - 157 notes: 1. true position applies to pins at the base plane (datum c). 2. true position applies at the pin tips. 3. the lid is electrically connected to vss. 4. letter designations are for cross-reference to mil-std-1835. 5. lead finish is in accordance with mil-prf-38535. 6. coplanarity is not measured. figure 60. s m mmit xte 139-pingrid array b
s m mmit family - 158 figure 61. s m mmit xte 140-lead flatpack notes: 1. all exposed metalized areas are gold plated over nickel plating per mil-prf-38510. 2. the lid is electrically connected to vss. 3. lead finish is in accordance with mil-prf-38535. 4. letter designations are to cross-reference to mil-std-1835. 5. lead true position tolerances and coplanarity are not measured. (full length of lead) b 0.008 + 0.002 typ. 0.020 m c a m b m 0.007 m c
s m mmit family - 159 26.0 o r d e r i n g i n f o r m a t i o n enhanced s m mmit e mil-std-1553 dual redundant bus controller/remote terminal monitor ut 69151 * * * * lead finish: (a) = solder (c) = gold (x) = optional screening: (c) = military temperature (p) = prototype package type: (g) = 85-pin pga (w) = 84-lead fp (f) = 132-lead fp (.025 pitch, ncs) e = smd device type 03 (non-radhard) c = smd device type 04 (non-radhard) notes: 1. lead finish (a,c, or x) must be specified. 2. if an ?x? is specified when ordering then the part marking will match the lead finish and will be either ?a? (solder) or ?c? (go ld). 3. military temperature range devices are burned-in and tested at -55 c, room temperature, and -125 c. radiation neither tested nor guaranteed. 4. lead finish is at utmc?s option. "x" must be specified when ordering. radiation neither tested or guaranteed. enhanced s mmm it e mil-std-1553 dual redundant bus controller/remote terminal monitor: smd 5962 * * * * * * lead finish: (a) = solder (c) = gold (x) = optional case outline: (x) = 85-pin pga (non-radhard only) (y) = 84-pin fp (z) = 132-lead fp (.025 pitch, ncs) (non-radhard only) class designator: (v) = class v (q) = class q device type: (04) = radhard enhanced s m mmit (03) = non-radhard enhanced s m mmit drawing number: 92118 radiation: - = none (f) = 3e5 (300krad) (r) = 1e5 (100krad) notes: 1. lead finish (a,c, or x) must be specified. 2. if an ?x? is specified when ordering, part marking will match the lead finish and will be either ?a? (solder) or ?c? (gold). 3. device type 03 not available as rad hard.
s m mmit family - 160 enhanced s m mmit lxe/dxe mil-std-1553 dual redundant bus controller/remote terminal/monitor/transceiver multichip module lead finish: (a) = solder (c) = gold (x) = optional screening: (c) = military temperature (p) = prototype package type: (g) = 96-pin pga (w) = 100-lead fp device type modifier: (lxe12) = +5v/-12v operation (lxe15) = +5v/-15v operation (dxe) = +5v operation - = smd device type 07, 08 (non-radhard) c = smd device type 10, 11 (non-radhard) notes: 1. lead finish (a,c, or x) must be specified. 2. if an ?x? is specified when ordering then the part marking will match the lead finish and will be either ?a? (solder) or ?c? (gold). 3. military temperature range devices are burned-in and tested at -55 c, room temperature, and -125 c. radiation neither tested nor guaranteed. 4. prototype lead finish is gold only. lead finish is at utmc?s option. ?x? must be specified when ordering. radiation neither test ed or guaranteed. enhanced s m mmit lxe/dxe: mil-std-1553 dual redundant bus controller/remote terminal/monitor/ transceiver multichip module: smd 5962 * * * * * * notes: 1. lead finish (a,c, or x) must be specified. 2. if an ?x? is specified, part marking will match the lead finish and will be either ?a? (solder) or ?c? (gold). lead finish: (a) = solder (c) = gold (x) = optional case outline: (x) = 96-pin pga (non-radhard) (y) = 100-lead fp class designator: (v) = class v (q) = class q device type: (10) = rh summit lxe15 (11) = rh summit dxe5 (07) = non-rh summit lxe15 (08) = non-rh summit dxe5 (09) = non-rh summit lxe12 drawing number: 94663 radiation: - = none (f) = 3e5 (device type 11 only) (300k rad) (r) = 1e5 (device type 10 & 11 only) (100krad) ut 69151 * * * * *
s m mmit family - 161 enhanced s m mmit xte mil-std-1553 dual redundant bus controller/remote terminal/monitor/transceiver multichip module radiation: none lead finish: (a) = solder (c) = gold (x) = optional screening: (c) = military temperature (p) = prototype package type: (g) = 139-pin pga (w) = 140-pin fp device type modifier: (xte12) = +5v/-12v operation (xte15) = +5v/-15v operation (xte) = +5v operation notes: 1. lead finish (a,c, or x) must be specified. 2. if an ?x? is specified when ordering then the part marking will match the lead finish and will be either ?a? (solder) or ?c? (gold). 3. military temperature range devices are burned-in and tested at -55 c, room temperature, and -125 c. radiation neither tested nor guaranteed. 4. prototype asembly are tested at +25c only. lead finish is gold only. radiation neither tested or guaranteed. enhanced s m mmit xte: mil-std-1553 dual redundant bus controller/remote terminal/monitor/transceiver multichip module: smd 5962 * * * * * * notes: 1. lead finish (a,c, or x) must be specified. 2. if an ?x? is specified, part marking will match the lead finish and will be either ?a? (solder) or ?c? (gold). 3. device types 04, 05, 06 available until 4q98. 4. device types 07, 08, 09 available after 4q98. lead finish: (a) = solder (c) = gold (x) = optional case outline: (x) = 139-pin pga (y) = 140-pin fp class designator: (q) = class q device type: (04) = summit xte 5v/15v (05) = summit xte 5v (06) = summit xte 5v/12v (07) = summit xte 5v/15v (4q98) (08) = summit xte 5v/5v (4q98) (09) = summit xte 5v/12v (4q98) drawing number: 94758 radiation: none ut 69151 - * * * * *

▲Up To Search▲

Price & Availability of 5962-9466309QXC

	To Download 5962-9466309QXC Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .